Skip to main content

Set Up JavaScript Tags for Campaign Data Collection

Learn how to set up JavaScript tags to track impressions, clicks, and conversions from your campaigns across supported advertising platforms

J
Written by Juan Sebastian Franco
Updated over 3 months ago

JavaScript tags allow you to capture impressions, clicks, and conversions from your campaigns, helping you:

  • Measure campaign performance based on actual user interactions.

  • Build audience segments from campaign-engaged users.

  • Retarget users across different advertising platforms.

  • Optimize ad spend by tracking conversion effectiveness.

Types of JavaScript Tags

Loop provides three JavaScript tags for campaign tracking:

  • Impression Tag – Captures when an ad is displayed.

  • Click Tag – Captures when a user clicks on an ad.

  • Conversion Tag – Captures when a user completes a conversion action.

The availability of these tags depends on the DSP or campaign manager being used.

How to Generate JavaScript Tags in Loop

  1. Go to Sources in the Loop platform.

  2. Click Create New.

  3. Select Advertising (JavaScript).

  4. Choose the platform where the snippet will be placed. The snippet will vary depending on the platform and will include necessary variables (e.g., campaign ID, creative ID).

  5. Loop will display the three JavaScript tags:

    • Impression Tag

    • Click Tag

    • Conversion Tag

  6. Copy the relevant tags and follow the platform’s documentation to set them up.

Supported Platforms

Loop supports JavaScript tags for the following advertising platforms:

  • Smart Adserver

  • E-Planning

  • Google DV360

  • Pubmatic

  • AppNexus

  • Google Campaign Manager 360 (formerly DoubleClick CM)

  • Sizmek

  • Google Ads

  • Google DV360 for YouTube

  • Meta

  • Generic "Others" option for unsupported platforms

Using Tag Manager for Google & Meta Tags

For platforms such as Google Ads, Campaign Manager 360, and Meta, JavaScript tags can be deployed directly through Google Tag Manager (GTM) and triggered by relevant platform events.

External Documentation for Platform-Specific Setup

Did this answer your question?