Skip to main content
Deploy Invoca on Google AMP pages using a dedicated AMP-compatible code snippet, which requires one tag per phone number instead of one tag per page.
For most landing pages, you use the Invoca Tag Wizard to generate a normal Tag snippet to paste into your page’s code. You can also use Invoca with Google AMP pages — your AMP tag has the same options as your regular Invoca Tag, but uses a different, AMP-compatible code snippet. A few differences to be aware of:
  • Unlike your usual Invoca Tag, your AMP tag code snippet doesn’t automatically update when you change your Invoca Tag settings.
  • You must create a separate AMP tag for each destination phone number on your AMP page that you want to swap with Invoca promo numbers.

Finding and deploying your AMP snippet

  1. Log in to your Invoca account. In the sidebar menu, click Settings, then in the Network section, select Invoca Tags.
  2. If you have more than one Invoca Tag, select the one you want to use. Scroll to the Code Snippets tile and click the Google AMP tab.
  3. Copy the code snippet, then paste it into the code of your AMP page.
  4. Each AMP page must also include the AMP call tracking script, along with the Invoca AMP tag:

Building a tag

Since the AMP tag is static, you’ll need to create one tag per number to be replaced on the AMP page. Start by entering the number to replace, or selecting from the available numbers listed in the associated Invoca Tag. Then select the campaign you want applied to that number from the dropdown. The AMP tag generates as you fill out each section. At this point, the AMP tag will replace the number and attribute it to the selected campaign. To capture additional attribution information, you can also capture Client ID, referrer, or available URL parameters. Define the parameter name you want the Client ID to appear in. If the Client ID isn’t available for a given user, AMP attempts to find a Client ID cookied under the Cookie Name you provide. If user consent is required to capture Client ID, Invoca waits to capture it until the defined consent parameter is detected. Invoca can also capture URL parameters when available, or use a fallback value you define. Defined parameters must be existing RingPool parameters or Marketing Data fields, but the fallback value can be anything. Once configured, the AMP tag is ready to deploy. Wrap the number you want replaced with an <a href> tag, for example:
NoteAMP tags work the same as Invoca tags if the RingPool is in overflow.

Using AMP with Destinations

If you’re using the Destinations feature, the Number to Replace determines which Destination is used. If you already have a Destination created that you want to use, enter its Website Phone Number as the Number to Replace. If no matching Destination exists, one is created automatically the first time the AMP tag loads. Selecting a Destinations-enabled campaign automatically updates the AMP code snippet to include:
If you don’t have auto-promote enabled, you’ll need to promote the Website Phone Number from the Discovered Page before tracking numbers start associating with the Destination.

Where to go next

Last modified on September 21, 2026