Connect Google Tag Manager

With Google Tag Manager connected, Vipter loads your container on the checkout and the thank-you page and pushes each event to the dataLayer, using the GA4 e-commerce standard. Inside GTM, you decide which tags fire on each event. Use GTM for platforms Vipter doesn't connect directly or for tags you already maintain there.

Before you start, it helps to read how conversion tracking works.

Step 1: copy the container IDCopy Anchor Link

In Google Tag Manager, open the Web container. The ID shows at the top of the workspace and starts with GTM-, such as GTM-AB12CD3. Copy this ID.

Step 2: connect the account in VipterCopy Anchor Link

1. In the Vipter dashboard, open General›Conversions›Accounts and click Connect account. Choose Google Tag Manager.
2. Fill in the numbered fields.

3. Click Connect and verify and then Continue.
4. Check the products where the container should load and click Finish. Turn on Use automatically on new products to include products created later.

Step 3: create the triggers in GTMCopy Anchor Link

Vipter doesn't create anything inside your container. For a tag to fire on a checkout event:

1. In GTM, create a Custom Event trigger with the event name, such as purchase. The list of names is in the table below.
2. To read the value, the currency or the order ID, create Data Layer Variables, such as ecommerce.value, ecommerce.currency and ecommerce.transaction_id.
3. Attach the trigger to the tags that should fire and publish the container.

Each event reaches the dataLayer in this format:

dataLayer.push({ ecommerce: null }); // clears the previous event
dataLayer.push({
  event: 'purchase',
  event_id: 'ord_…:purchase',
  vipter_event: 'purchase',
  payment_type: 'pix',
  ecommerce: {
    currency: 'BRL',
    value: 197,
    transaction_id: 'ord_…',
    items: [{ item_id: '…', item_name: 'Example course', price: 197, quantity: 1 }],
  },
  user_data: { email: 'buyer@example.com', phone_number: '…' },
});

• event_id is the same identifier Vipter uses in server deliveries. Use it as the event ID in tags that deduplicate.
• vipter_event is the event's name in Vipter, the same across all platforms.
• transaction_id only exists once there is an order.
• user_data is only sent with Email on under Matching data. The phone is sent with Phone on. The data goes as the buyer typed it, without hashing.

Step 4: testCopy Anchor Link

1. In GTM, open Preview mode and enter the checkout address of a product linked to the account.
2. Go through the checkout. Each event shows in the preview list with the dataLayer data.
3. In Vipter, the account's Connection tab shows when the first event was received, after someone fills in their details on the checkout.

What Vipter sends to the dataLayerCopy Anchor Link

• The page view goes as vipter_page_view, not as page_view. Use this name in the trigger.
• Renewal and Refund / chargeback don't reach GTM, because they happen after the buyer has left the checkout.
• In What to send, choose the events, the Conversion value and the Value currency. See events and values.

Common problemsCopy Anchor Link

• Invalid format on the ID field

  The ID must start with GTM-. Don't paste the whole install snippet or a GA4 ID (G-).

• Purchases show up twice in GA4 or Meta

  The same platform is connected directly in Vipter and also has a tag inside GTM. Keep only one of the two paths.

• The tags don't fire

  The container wasn't published after creating the triggers, or the event name in the trigger doesn't match the table. Names are case-sensitive.

• Nothing loads when the buyer declines cookies

  With the consent banner on, the container only loads after the buyer accepts.

What to do nextCopy Anchor Link

• Connect Google Analytics 4 directly in Vipter to also count the sales confirmed by the server.
• Paste the UTM script on your sales page to keep the visit's source all the way to the checkout.