Google Tag Manager

Prev Next
The August 2024 release changed the Google Tag Manager’s default behavior.

By default, Google Analytics cookies will only be collected when the Cookies Consent Banner is enabled. Previously, analytics were collected when the banner was disabled.

For customers who have not enabled the cookie consent banner, tracking was mistakenly disabled as of August 27, 2024.

If you wish to re-enable tracking, please contact Blackthorn Support, and we will apply the necessary flag to your account. Please include your org ID and desired configuration.

Configuration options:

  • Enable tracking analytics with a cookie consent banner in place (recommended)
  • Enable tracking analytics without a cookie consent banner in place (pre-August 27th default behavior; not recommended)

Google Analytics can provide the important insights you’re looking for. However, when used alone, Google Analytics has limitations. By using Google Tag Manager in conjunction with Google Analytics, you can collect more data on Attendees.

Click here to see the full list of supported tags. Blackthorn supports everything in the Web column.

Prerequisite

If you are using Google Tag Manager, please reach out to Blackthorn Support to enable cookies for your Attendees and to ensure data laws have been considered.

Set up Google Tag Manager

  1. Go to the Tag Manager.
  2. Sign into your Google account.
  3. Click the Accounts tab.
  4. Click Create Account.
  5. Enter an Account Name.
  6. Select a Country.
  7. Enter “events.blackthorn.io” (http://events.blackthorn.io/) in the Container name field.
  8. Select “Web” for the Target platform.
  9. Click Create.

You will receive the installation code snippet for your website.

Set Up Variables

  1. Go to the Variables section.
  2. Click Configure.
  3. Select all checkboxes under the "Clicks", "Forms," and "History" sections.

Set Up Triggers

  1. Go to the Triggers section.
  2. Click New.
  3. Set Trigger Type to “History Change.”
  4. Select "All History Changes" in the "This trigger fires on" section.
  5. Click Save.
  6. Enter a name for the trigger.

Set Up Tags

  1. Go to Tags section.
  2. Click New.
  3. Enter a Tag name.
  4. Set the Tag type to “Google Tag."
  5. Enter the measurement id (or Google Analytics Id) in the Measurement Id field. (See the last step in Create a (GA4) Google Analytics Account.)
  6. Click Trigger Configuration.
  7. Select the “History Change” trigger type. (unless you changed the name)
  8. Click Save.
  9. Go to the Overview section.
  10. Copy/save the “GTM-“ code/id.

“GTM-“ ID Criteria

The ID must meet the following criteria:

  • The ID starts with “GTM-“
  • Includes only valid characters (uppercase letters and numbers)
  • The format matches “GTM-XXXXXXX” (prefix GTM- followed by 6–10 uppercase letters/numbers).

Update Your Company Info Record

  1. Go to your Salesforce org.
  2. In the App Launcher, enter “Company Info” and click the link.
  3. Open an existing Company Info record or create a new one.
  4. Confirm that the Google Tag Manager ID and Use for All Events fields are displayed on the page layout. If they aren’t, add them.
  5. On the Company Info record, enter the Google Tag Manager ID in the Google Tag Manager ID field.
  6. Set Use for All Events = "True" (checked).
  7. Click Save.

Event-Level Configuration

The Event Settings object now includes the GTM Container ID (conference360__GTM_Container_ID__c) field, enabling Event-level configuration of Google Tag Manager (GTM).

This field stores the Google Tag Manager (GTM) container ID for the Event. When populated, this Event-level setting overrides the org-level GTM configuration and is used by the Event's webapp to load the GTM on Event pages and in embedded registrations.

The following logic explains when and how the Google Tag Manager ID is applied.

  1. The Google Tag Manager ID set at the Event level (Event Settings GTM Container ID) will override the Google Tag Manager ID set at the company level (Company Info Google Tag Manager Id).
  2. If the Event Settings GTM Container ID field is blank, the Google Tag Manager ID will default to the value in the Company Info Google Tag Manager Id field.
  3. If neither field contains a value, the Google Tag Manager ID will be blank.

Update an Event Settings Record

  1. If the GTM Container ID field hasn’t been added to the (Event Settings page layout, add it now.
    1. Go to Setup.
    2. Click the Object Manager tab.
    3. In the Quick Find box, enter and click “Event Settings.”
    4. Click the Page Layout Tab.
    5. Locate the GTM Container ID field and drag and drop it onto the page layout.
    6. Click Save.
  2. Open the (Event Settings record associated with the Event. (If the record was already open, refresh the page.)
  3. Click the Pencil icon next to the GTM Container ID field.
  4. Enter the Google Tag Manager ID in the GTM Container ID field.
  5. Click Save.

You should now see traffic reports on your Google Analytics account. Please note: If the account is new, it may take up to 48 hours for the first traffic events to appear in Google Analytics.

Iframes

If you are using the Google Tag Manager with iframes, please ensure your CSP restrictions allow adding iframes from other domains. If allowed, the Google Tag Manager will generate an iframe to perform the tracking on your site.

If you don't want to relax CSP rules, please add the following cross domain frames:

  • https://*.google.com
  • https://*.gstatic.com
  • https://*.google-analytics.com
  • https://*.googletagmanager.com

Test Your Setup

To confirm that everything was configured correctly, complete the following steps.

  1. Create and publish a new Event record in your Salesforce org.
  2. Copy the Event’s Event Page URL.
  3. Go to your Google Tag Manager account.
  4. Click the Preview button.
  5. Enter the copied Event Page URL in the “Your Website URL” field.
  6. Click Connect.

Two new tabs will appear. One will show the Event’s web page. The other will be a debug page with the tags that were identified on the Event web page.

If you see your tag in the Summary’s “Tags not fired” section, then everything was configured correctly.