Skip to main content

Implementing the M2O Pixels in GTM with Consent Mode.

Learn how to set up Match2One tracking pixels in Google Tag Manager (GTM) while respecting user privacy with Google Consent Mode.

Updated this week

Note: Your CMP (cookie banner) must send consent information to GTM’s Consent Mode. If this is not yet implemented, please ensure your CMP provider (e.g., Cookiebot, OneTrust) is connected to GTM’s Consent API.

Important notice: IDs provided by Match2One.

Step 1A — Create the Tag Pixel Loader

Steps:

  1. In GTM, go to Tags → New → Tag Configuration → Custom HTML→ paste the loader script.

Paste the following code you achieved in a .txt file or downloaded from your account in the Match2one platform. In the Custom HTML container. See screenshot below.

Important: This loader must fire only once per page load. Do not add any additional triggers like History Change.

3. To find the pixel code in Match2One go to the tracking Menu (Blue Box) an press the cog wheel icon (Red Box). See screenshot below.

4. Name the tag, for example:

M2O - Pixel Loader

5. Click Save

Step 1B — Create the Trigger

Steps:

  1. In GTM, go to Triggers → New → Trigger Configuration → Consent Initialization

  2. Under Tag Firing Options, choose: All Pages

  3. Name the trigger, for example:
    ​ M2O - Pixel Loader Trigger

  4. Click Save

Example of correct trigger setup for the Loader tag – use “Consent Initialization – All Pages”.

Step 2A — Create the PageView Event Tag

This is the tag that fires the actual PageView event.

Steps:

  1. In GTM, go to Tags → New → Tag Configuration → Custom HTML

  2. Paste the following code:

3. Under code, open “Advanced Settings → Consent Settings and check “Require additional consent for tag to fire”.

(This tag will only fire if the status of all of the specified consent types is 'granted' when the tag is triggered.)

Click “+add required consent” and insert CMP requested consent types as for example:

  • ad_storage

  • ad_user_data

  • ad_personalization

4. Name the tag, for example: M2O - PageView [All Pages]

5. Click Save

Example of the correct Consent Settings for M2O event tags (PageView, SignUp, FTD). Select “Require additional consent” and add ad_storage, ad_user_data, and ad_personalization.

Read more here https://support.google.com/tagmanager/answer/10718549?hl=en

Step 2B — Create the Trigger

Steps:

  1. In GTM, go to Triggers → New → Trigger Configuration → Page view

  2. Under Tag Firing Options, choose: All Pages

  3. Name the trigger, for example:
    ​ M2O - PageView [All Pages] Trigger

  4. Click Save

Step 3A — Create the Conversion Event Tag

This step describes setting up any conversion event, such as SignUp or FirstTimeDeposit.

You need to do one event per pixel.

These event pixels are available:

  • Landingpage

  • ItemView

  • AddToCart

  • InitiateCheckout

  • AddPaymentInfo

  • Purchase

  • Lead

  • SignUp

  • FirstTimeDeposit

  • Deposit

Steps:

  1. In GTM, go to Tags → New → Tag Configuration → Custom HTML

  2. Paste the following code:

For example, this tag fires when a user makes their first deposit.

3. Variable names (in red between < >: Should be changed to the correct variable names in

GTM, as they are named. Copy the Variable name and replace the placeholders with your GTM variables or dynamic values:

  • <ORDER_ID> → the unique deposit or transaction ID

  • <ORDER_VALUE> → the deposit amount

  • <ORDER_CURRENCY_CODE> → the currency (e.g. "USD", "SEK", "EUR")

The placeholders should be replaced or mapped from GTM variables (for example, {{Transaction Value}} and {{Currency}}).

It’s necessary to change the icons < and > to brackets {{ and }} in each placeholder.

If the variable contains text data, wrap it with single quotes ' ' — for example:

order_currency_code: '{{Currency}}'

If the variable contains numeric values, don’t add any quotes — for example:

order_value: {{Transaction Value}}

4. Under code, open “Advanced Settings. Go to “Require additional consent for tag to fire” (This tag will only fire if the status of all of the specified consent types is 'granted' when the tag is triggered.)

5. Click on “add required consent” and insert:

a) ad_storage

b) ad_user_data

c) ad_personalization

6. Name the tag, for example:
​M2O - FTD - FirstTimeDeposit

7. Click Save

Step 3B — Create the Trigger

Steps:

  1. In GTM, go to Triggers → New → Trigger Configuration → Custom Event

  2. Enter the event name (e.g., signup_success, firsttimedeposittd, deposit) in the placeholder.

  3. Under Tag Firing Options, choose: All Pages

  4. Name the trigger, for example:
    ​ M2O - FTD - FirstTimeDeposit Trigger

  5. Click Save

Summary:

Tag

Trigger

Consent Settings

Loader

Consent Initialization – All Pages

(none needed)

PageView

All Pages

ad_storage,

ad_user_data,

ad_personalization

SignUp

Custom Event → sign_up

ad_storage,

ad_user_data,

ad_personalization

FTD

Custom Event → ftd

ad_storage,

ad_user_data,

ad_personalization

Explanation:

  • Loader tag: loads the M2O script on every page before other tags fire. It doesn’t need consent gating.
    ​

  • PageView tag: fires on all pages but only after the user has granted consent.
    ​

  • SignUp tag: fires when your dataLayer sends an event called sign_up, but only if consent is granted.
    ​

  • FTD tag: fires when the dataLayer sends ftd (first time deposit), also gated by consent.

Before publishing your container

  • Test in GTM Preview Mode
    ​

  • Check the Consent Overview tab.
    ​

  • Verify that tags are fired only after consent is granted.
    ​

  • Confirm events (PageView, SignUp, FTD) appear in network logs.

Single Page Application (SPA) installation in GTM

If you're working with a single-page application, here's how to track your Page views.

Step 2:1A — Create the PageView Event Tag [Initial]

This is the tag that fires the actual PageView event.

Steps:

  1. In GTM, go to Tags → New → Tag Configuration → Custom HTML

  2. Paste the following code:

3. Under code, open “Advanced Settings. Go to “Require additional consent for tag to fire”

(This tag will only fire if the status of all of the specified consent types is 'granted' when the tag is triggered.)

Click on “add required consent” and insert CMP requested consent types, for example:

● ad_storage

● ad_user_data

● ad_personalization

4. Name the tag, for example: M2O - PageView [Initial]

5. Click Save

Example of the correct Consent Settings for M2O event tags (PageView, SignUp, FTD). Select “Require additional consent” and add ad_storage, ad_user_data, and ad_personalization. Read more here https://support.google.com/tagmanager/answer/10718549?hl=en

Step 2:2B — Create the Trigger [Initial]

Steps:

  1. In GTM, go to Triggers → New → Trigger Configuration → Page view

  2. Under Tag Firing Options, choose: All Pages

  3. Name the trigger, for example: M2O - PageView [Initial] Trigger

  4. Click Save

Step 2:2A — Create the PageView Event Tag [SPA]

This is the tag that fires the actual PageView event.

Steps:

  1. In GTM, go to Tags → New → Tag Configuration → Custom HTML

  2. Paste the following code:

3. Under code, open “Advanced Settings. Go to “Require additional consent for tag to fire”

(This tag will only fire if the status of all of the specified consent types is 'granted' when the tag is triggered.)

Click on “add required consent” and insert CMP requested consent types, for example:

● ad_storage

● ad_user_data

● ad_personalization

4. Name the tag, for example: M2O - PageView [SPA]

5. Click Save

Example of the correct Consent Settings for M2O event tags (PageView, SignUp, FTD). Select “Require additional consent” and add

ad_storage, ad_user_data, and ad_personalization.

Read more here https://support.google.com/tagmanager/answer/10718549?hl=en

Step 2:2B — Create the Trigger [SPA]

Steps:

  1. In GTM, go to Triggers → New → Trigger Configuration → History Change

  2. Under Tag Firing Options, choose: All History Changes.

3. Name the trigger, for example: M2O - PageView [SPA] Trigger

4. Click Save

Step 2:2B:X — Create the Trigger [SPA] ADVANCED

Steps:

5. In GTM, go to Triggers → New → Trigger Configuration → History Change

6. Under Tag Firing Options, choose: This trigger fires on:

  • {{Page URL}} Does not contain #

  • {{History Source}} matches RegEx pushState|replaceState

7. Name the trigger, for example: M2O - PageView [SPA] Trigger

8. Click Save

Have any questions?

Feel free to reach out to our support: customer.support@match2one.com

Did this answer your question?