All marketplaces require you to provide a SaaS URL that could be a registration page or direct login for each product you are selling. That way, buyers who initiate a transaction on the marketplace can register on your website. While you can host a registration page in your company's domain, the benefits of using a Tackle-hosted registration page are:
It is included with your Tackle subscription.
No engineering is required to set up the page.
All buyer registration details will be sent to you from Tackle.
You have some flexibility in how the registration page will look and flow.
You can use the Tackle-hosted registration page or your own self-hosted registration page.
Select the Tackle-hosted registration page
In Tackle, go to the left menu and click Listings🔗.
Select your product listing.
Click Registration Details.
Select Tackle hosted.
Here you can see the registration page that has already been built for you by Tackle and make any necessary edits. These edits will take effect immediately.
Select the self-hosted registration page
In Tackle, go to the left menu and click Listings🔗.
Select your product listing.
Click Registration Details.
Select Self-hosted.
Here you can input the registration link that was configured by your developers.
Set up your own self-hosted registration page
Next, create a registration page for your product, hosted on a public URL so all your marketplace buyers can access it. You must include the following query parameters on your registration page so information can flow from your self-hosted registration back to Tackle. Additionally, your page must be able to receive GET requests from Tackle (303 redirects), which we use to help prevent errors.
Why does Tackle send GET requests to your self-hosted page?
Tackle follows a web development best practice called Post-Redirect-Get (PRG) to prevent certain common errors in form submissions. This involves sending a 303 redirect to your registration page as a GET request to prevent duplicate POST requests. For a full view of how data flows between Google Cloud, your self-hosted registration page, and Tackle, see the diagram below.
These query parameters are set when Tackle calls your self-hosted registration page URL:
Customer ID (<cloud>_customer_id)
Product ID (<cloud>_product_id)
Important: Offer type will only be set for free trial offers and will then have a value of free-trial.
Use the correct query parameter names for the Google Cloud Marketplace:
gcp_customer_id <string>
gcp_product_id <string>
Send Tackle your self-hosted registration page information
Once you select the Self-hosted registration page and input your registration page link, all buyers who initiate transactions with you in the marketplace will be sent to your self-hosted registration page. They will need to enter required information (the buyer's company name, full name and email) and any other registration details you request.
Once your self-hosted registration page is live, use the
customeridandproductidas request body parameters in the Tackle Registration API🔗 to send the buyer's registration information to Tackle. The fields correspond to the fields defined in the registration page fields for a given listing. You can also set registration details in your listing registration page and these will be sent back to Tackle as described in the Tackle Registration API🔗.
Tip
You can use information gathered from your self-hosted registration page to build your own automated fulfillment processes (like auto-provisioning).