Button

CJ Button Integration Setup Guide

Enable mobile tracking for CJ advertisers via Button redirection — supporting in-app actions and SMS campaigns.

Active cjevent tracking must be configured for attribution before starting.
Standard integration setup is required — custom or complex configurations require additional review with CJ support.
AID/PID/SID attribution methods are NOT compatible with Button integration.

Button integration enables mobile tracking for CJ advertisers, redirecting traffic through Button's endpoint for enhanced mobile experiences. This integration supports in-app action tracking and SMS campaigns while maintaining standard CJ attribution through cjevent.

Button tracking is not impacted by Apple's App Tracking Transparency policy or IDFA loss, as Button does not require IDFA or use it for attribution.

In-App Action Tracking (Reach)

Button supports in-app action tracking through the Reach integration, enabling tracking of sales and installs for both iOS and Android applications.

SMS Integration

Button's SMS integration re-engages customers who visit your site but don't immediately convert.

Button Link Structure

Traffic redirects through Button's endpoint r.bttn.io immediately after integration begins.
By default, Button passes customers to the standard web experience.
Button can configure experiments to redirect specific traffic percentages to in-app or mobile interstitial experiences.

Required URL Parameters

Parameter	Description	Example
btn_url	URL-encoded final landing page (determines in-app destination)	http%3A%2F%2Fwww.example.com
btn_ref	CJ traffic identifier (hardcoded for all CJ traffic)	org-6658d51db36e0f38
btn_reach_pub	Publisher ID for Button reporting	{pid}
btn_mobile_url	URL-encoded fallback URL for desktop/mobile web	http%3A%2F%2Fwww.example.com
btn_network_ref	Captures cjevent value for server-to-server tracking	{eventId}
btn_cj_sid	SID tracking for SMS advertisers	{url(sid)}

Updated about 1 month ago

Did this page help you?