Setup AdPage container
Go from sign-up to your first deploy in under five minutes.
This quickstart is about getting you to your first deploy fast. We're going to skip most of the setup for now, since you can always go back and tweak things once you've got something up and running.
Create your AdPage Container
Register and create your account
Go to AdPage and register or log in. Follow the steps to set up your account and fill in the info it asks for. You'll need to pick whether you're a client or an agency. The difference comes down to who you're setting up containers for. Go with client if it's for your own website or websites, and agency if you're setting them up for your clients.
Server container configuration
To get your AdPage server container going, you'll need to hook it up to a Google Tag Manager server container. After that, connect it to the root domain using CNAME cloaking. The last step is swapping out the standard Google Tag Manager script on the website for a Tagging Pixel.
Connect your AdPage container with your Google Tag Manager server container
You can connect your AdPage server container to a Google Tag Manager server container with Google's base64 configuration code. That way you can set up your tracking rules on the Google Tag Manager server container.
Manually retreive the base64 configuration code
If you'd rather set up the Google Tag Manager server container connection by hand, you'll need to grab the base64 code yourself. Go to Google Tag Manager and open your server container, or make a new one if you don't have one yet. You'll find the configuration code in the Container settings inside the server container admin. It shows up once you click the "Set up your tagging server" button.
Configure DNS records
To use AdPage server-side tagging, you'll need to set up a custom domain. This is also called a custom tagging server URL, and it's what lets you set first-party cookies and use the AdPage Tagging Pixel. Make sure the URL uses the same root domain as your website.
Log in to wherever you manage your domain and create a new DNS record for the subdomain you want to use. It's a CNAME record, and you'll find the Host and Target values in the registration instructions.
Tagging Pixel
Step 3 of the container registration is to replace the Google Tag Manager script on the website with an AdPage Tagging Pixel. This Tagging Pixel has the same functionality as a Google Tag Manager script, it sets up the connection between the website and your Google Tag Manager web container.
Add your Website URL, add the Google Tag Manager Web Container ID. These two inputs are needed to generate the Tagging Pixel script and set up the Tagging Pixel verification.
Once you've added those two, you can generate the Tagging Pixel instructions. You'll get different instructions depending on which Content Management System (CMS) you use. AdPage has an App for Shopify, a Plugin for Wordpress and WooCommerce, a Module for Magento, and its own set of instructions for Lightspeed, which also add an e-commerce dataLayer to the front end of the website. If all you need is the Tagging Pixel script, pick the custom CMS option to get the code for the <head> and <body>.
What's next?
Once you've added your first client or container, you can move on to setting up the tracking rules in your Google Tag Manager web and server containers. The next step goes over what you need to set up in your Google Tag Manager server container.
If you are setting up server-side tagging for a Shopify, WooCommerce, Magento or Lightspeed webshop. You can skip ahead to these steps: Using AdPage Templates.
Last updated
Was this helpful?