Skip to main content
Supported URL Parameters

This article shows which URL parameters are supported when using the Lunio on site script.

Updated yesterday

Lunio On-Site Script: Supported Tracking Parameters

The Lunio on-site script determines the source of clicks using URL tracking. In many cases, your existing tracking setup will be compatible with Lunio, requiring no changes. Below, you'll find a list of supported parameters, along with an optional custom parameter should your tracking not align with the supported values.


Supported Tracking Parameters by Platform

Google

  • Supported Parameters: utm_source=google or youtube, or a gclid, wbraid, or gbraid click identifier.

  • Custom Parameter: ppcp_platform=google

  • Additional Notes: Auto-tagging should be enabled so that click IDs are automatically applied, requiring no additional configuration. If you have a unique use case, you can find more details on applying tracking within Google Ads here.

Meta (Facebook, Instagram, WhatsApp)

  • Supported Parameters: utm_source=facebook, instagram, meta, whatsapp, fb

  • Custom Parameter: ppcp_platform=meta

  • Additional Resources: More information on managing your Meta URL tracking can be found here.

X (Twitter)

  • Supported Parameters: utm_source=twitter, or a twclid click identifier.

  • Custom Parameter: ppcp_platform=twitter

  • Additional Notes: URLs must be manually edited to include tracking parameters.

Pinterest

  • Supported Parameters: utm_source=pinterest, or an epik click identifier.

  • Custom Parameter: ppcp_platform=pinterest

  • Additional Resources: More information on managing Pinterest tracking parameters can be found here.

TikTok

  • Supported Parameters: utm_source=tiktok, or a ttclid click identifier.

  • Custom Parameter: ppcp_platform=tiktok

  • Additional Resources: More details on TikTok tracking parameters can be found here.

Baidu

  • Supported Parameters: utm_source=baidu, or a bd_vid click identifier.

  • Custom Parameter: ppcp_platform=baidu

Reddit

  • Supported Parameters: utm_source=reddit, or an rdt_cid click identifier.

  • Custom Parameter: ppcp_platform=reddit

  • Additional Notes: URLs must be manually edited to include tracking parameters.

Adroll

  • Supported Parameters: utm_source=adroll

  • Custom Parameter: ppcp_platform=adroll

  • Additional Resources: More information on managing Adroll tracking parameters can be found here.

Naver

  • Supported Parameters: utm_source=naver, or a NaPm click identifier.

  • Custom Parameter: ppcp_platform=naver

Bing

  • Supported Parameters: utm_source=bing, or an msclkid click identifier.

  • Custom Parameter: ppcp_platform=bing

  • Additional Notes: If auto-tagging is enabled, no configuration is required. More details on managing Bing tracking parameters can be found here.

DV360 (Display & Video 360)

  • Supported Parameters: utm_source=dv360, or a dclid click identifier.

  • Custom Parameter: ppcp_platform=dv360

  • Additional Notes: If auto-tagging is enabled, no configuration is required. Otherwise, tracking parameters can be implemented either directly within DV360 or in CM360, depending on your setup.


If your platform or tracking setup is not covered above, you can use the custom parameter ppcp_platform=[your_platform] to ensure proper tracking with Lunio. If you need further assistance, feel free to reach out to our support team.

Did this answer your question?