Setting Up the Ceros Integration for Google Tag Manager

3 Minute read

Reading Time: 3 minute

If you are using Google Tag Manager (GTM), you can leverage the Ceros integration with GTM to send page view, click, and hover events to a tag configured in a GTM container. This means you can send your Ceros analytics (i.e. page views, clicks, hovers) back to Google Analytics or any other analytics platform you are using so that you can have all of your analytics in one place. And if you are already managing your tags through GTM, you can continue to do so with Ceros.

Setting up your GTM integration in Ceros:

  1. Copy your GTM Container ID
  2. In the Ceros Admin, select your name from the drop down and navigate to Account – Integration
  3. Toggle on the integration for Google Tag Manager
  4. Paste in your Container ID
  5. Toggle on Track Page Views for Standalone Experiences—page view events will not be sent if the experience is embedded
  6. Identify your Event Category, this will be used as the top-line grouping of the click/hover events
  7. Toggle on Track Clicks & Track Hovers and enter your Click Event Action and Hover Event Action values, these values will be sent back to identify your click and hover events
  8. Make sure that when creating your Ceros experience, each interaction is on a hotspot that is labeled with a specific name—the names of your hotspots are going to be the event values that identify what is being clicked and hovered over, so it’s very important to have unique names on these
  9. Hits save, and you’re good to go

The process above outlines how to set up your Google Tag Manager integration at an account level, however you also can set it up for specific experiences. To do this, navigate to the experience tile in the admin section and hover over it. Select the integrations button in the top right hand corner and toggle on the GTM integration. Next, follow steps 4-9 above to set up the integration for that specific experience.

What is sent via GTM?

The following data is sent when a page view, click, and/or hover is triggered on a standalone experience (i.e. living on its own URL). Data for embedded experiences should be handled by the parent page of the embed.

Page View Events:

dataLayer.push({
  event: "ceros-pageview"
  cerosPagePath: "/my-account/my-experience/p/1"
  cerosPageLocation: "http://view.ceros.com/my-account/my-experience/p/1"
  cerosPageTitle: "Overview Page"
});

Data Values:

  • event: This identifies the source of the page view event (Ceros) and is used as a trigger value for custom tags in the GTM container. This value cannot be changed.
  • cerosPagePath: The relative path and query params of the page URL.
  • cerosPageLocation: The full page URL (including query params).
  • CerosPageTitle: The title of the page set in the Ceros Studio

Click/Hover Events:

dataLayer.push({
	event: "ceros-event",
	cerosCategory: "ceros-event",
	cerosAction: "ceros-click",
	cerosLabel: "Outbound Link"
});

Data Values:

  • event: This identifies the source of the event (Ceros) and is used as a trigger value for custom tags in the GTM container. This value cannot be changed
  • cerosCategory: This value is used as a top-level grouping of the click/hover events. This can be configured in the integration options.
  • cerosAction: This is the name of the event being sent. The defaults are “ceros-click” and “ceros-hover” for click and hover events, respectively. These values can be configured in the integration options.
  • cerosLabel: This is the name of the object in the studio that is triggering the event (i.e. the name of the hotspot that the interaction was created on).

If you have any further questions about Google Tag Manager, feel free to ping our support team in the chat widget in the studio. And be sure to check out this article to learn more about setting up your Google Analytics Integration.

Was this helpful?

1 0
1 out of 1 people found this helpful