Platform Integration Guide
Connect your advertising platforms to Tandem Beam for automatic conversion tracking and attribution. This guide covers all 9 supported advertising platforms with step-by-step setup instructions.
Platform Comparison
| Platform | Difficulty | Setup Time | Click ID | Test Mode |
|---|---|---|---|---|
| ๐ Google Analytics 4 | 15 min | Auto-detected |
โ Debug endpoint | |
| ๐ Meta (Facebook) | 20 min | fbclid |
โ Test events | |
| ๐ผ LinkedIn | 30 min | li_fat_id |
โ Sandbox | |
| ๐ Google Ads | 25 min | gclid |
โ Test mode | |
| ๐ต TikTok | 20 min | ttclid |
โ Test events | |
| ๐ Pinterest | 20 min | Auto-captured |
โ Test mode | |
| ๐ค Reddit | 20 min | Auto-captured |
โ Sandbox | |
| ๐ฆ Twitter/X | 20 min | twclid |
โ Test mode | |
| ๐ Bing Ads | 20 min | msclkid |
โ Test mode | |
| ๐งช DEV+NULL | 5 min | N/A |
โ Always |
Before You Begin
What you'll need to successfully connect any advertising platform to Tandem Beam.
General Requirements
Active Tandem Beam Account
Your advertiser account must be created first
Platform Developer/Business Accounts
Most platforms require business-level accounts for API access
Admin/Owner Permissions
You'll need sufficient permissions to generate API credentials
15-30 Minutes
Setup time varies by platform complexity
Active Ad Campaigns
You should have active campaigns or pixels already set up
Basic Technical Comfort
Ability to copy/paste credentials and follow step-by-step instructions
Recommended for ClickBeam: CNAME Setup
If you're using ClickBeam (client-side tracking), we recommend setting up a CNAME record for improved reliability and first-party context.
Example: beam.yourdomain.com โ api.tandembeam.com
Common Terminology
| Term | What It Means | Example |
|---|---|---|
| Pixel ID | Unique identifier for your tracking pixel | 1234567890123456 |
| Access Token | Secret key that proves your identity to the platform | EAAGm0PX... |
| Click ID | Parameter added to URLs when someone clicks your ad | ?fbclid=xyz123 |
| OAuth | Secure authentication method used by most platforms | OAuth 2.0, OAuth 1.0a |
| API Secret | Secret key for server-to-server communication | abc123def456... |
| Conversion ID | Identifier for a specific conversion action or goal | 123456789 |
| Test Mode | Sandbox environment for testing without affecting real data | Debug endpoint, test events |
| URN | Uniform Resource Name - unique identifier format | urn:li:conversionRule:123 |
Setup Best Practices
โ Do
- โข Copy credentials carefully (no extra spaces)
- โข Use the "Test Connection" button after setup
- โข Keep credentials secure and never share publicly
- โข Start with easier platforms (GA4, Meta) first
- โข Document your credentials in a password manager
โ Don't
- โข Share access tokens in screenshots or emails
- โข Skip the test connection step
- โข Use production accounts for testing
- โข Mix up different platform credentials
- โข Forget to regenerate tokens if they expire
Quick Start: Easiest Platforms
Start with these three platforms for the fastest setup and immediate results.
๐ Google Analytics 4 (GA4)
Quick Facts
- Click ID: Auto-detected from GA4 cookies
- Authentication: Measurement ID + API Secret
- Test Mode: Debug endpoint available
- Events Supported: All standard events
Prerequisites
1 Access GA4 Admin
Log in to Google Analytics and navigate to Admin โ Data Streams
2 Find Your Measurement ID
Click on your Web data stream. Your Measurement ID is at the top right.
Format:
G-XXXXXXXXXX
Example: G-ABC123DEF4
3 Generate API Secret
In the same data stream, scroll down to Measurement Protocol API secrets โ Click Create
โ ๏ธ Important
Copy the API secret immediately - it won't be shown again!
4 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select Google Analytics 4 from dropdown
- Paste your Measurement ID
- Paste your API Secret
- Click Save Configuration
5 Test Your Connection
Click the Test Connection button and wait for validation (5-10 seconds)
โ Success!
You should see: "Successfully connected to GA4"
Troubleshooting
"Invalid Measurement ID" Error
Cause: Measurement ID format incorrect
Solution: Ensure it starts with "G-" and is exactly 10 characters after the hyphen
Check: Copy directly from GA4 admin (no extra spaces)
"Invalid API Secret" Error
Cause: API secret expired or incorrect
Solution: Generate a new API secret in GA4
Check: Ensure you copied the entire secret (typically 20+ characters)
๐ Meta (Facebook/Instagram)
Quick Facts
- Click ID: fbclid (Facebook Click ID)
- Authentication: Access Token + Pixel ID
- Test Mode: Test event codes supported
- Events Supported: purchase, lead, contact, add_to_cart, sign_up, view_content, initiate_checkout, page_view
Prerequisites
1 Access Meta Events Manager
Log in to Meta Business Manager โ Navigate to Events Manager โ Select your Data Source (Pixel)
2 Find Your Pixel ID
Your Pixel ID is at the top of Events Manager (15-16 digit number)
Format:
1234567890123456
3 Generate Access Token
Go to Settings โ Conversions API โ Click Generate Access Token
โ ๏ธ Important
Access tokens are sensitive. Keep them secure and never share publicly.
4 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select Meta (Facebook/Instagram)
- Paste your Access Token
- Enable Conversions toggle
- Paste your Pixel ID
- Click Save Configuration
5 Test Your Connection
Click Test Connection and look for green "โ Connected" status
โ Success!
You should see: "Successfully connected to Meta. Pixel ID verified."
Troubleshooting
"Invalid Access Token" Error
Cause: Token expired or incorrect permissions
Solution: Regenerate token with ads_management permission
Check: Ensure token hasn't been revoked in Business Manager
"Pixel Not Found" Error
Cause: Pixel ID doesn't exist or no access
Solution: Double-check Pixel ID (15-16 digits, no spaces)
Check: Verify you have access to this pixel in Events Manager
๐ผ LinkedIn
Quick Facts
- Click ID: li_fat_id (LinkedIn Click ID)
- Authentication: OAuth 2.0 Access Token
- Test Mode: Sandbox environment available
- Best For: B2B lead generation and conversions
Prerequisites
1 Access LinkedIn Campaign Manager
Log in to LinkedIn Campaign Manager โ Navigate to Conversion Tracking
2 Generate OAuth Token
In Campaign Manager โ Data Sources โ Conversions API โ Click Generate Token
Required scopes:
rw_conversions- Read and write conversionsr_ads- Read ad data
3 Find Conversion Rule URN
In Conversion Tracking, find your conversion rule and copy the URN
Format:
urn:li:conversionRule:123456
4 Configure in Tandem Beam
- Return to Platform Configurations
- Select LinkedIn from dropdown
- Paste your Access Token
- Enable Conversions toggle
- Paste your Conversion Rule URN
- Click Save Configuration
5 Test Your Connection
Click Test Connection to validate your credentials
โ Success!
You should see: "Successfully connected to LinkedIn"
Troubleshooting
"Invalid Token" Error
Cause: Token expired or incorrect scopes
Solution: Regenerate token with both rw_conversions and r_ads scopes
Check: Verify token hasn't been revoked
"Conversion Rule Not Found" Error
Cause: URN doesn't exist or no access
Solution: Verify URN format (urn:li:conversionRule:XXXXXX)
Check: Ensure conversion rule exists in Campaign Manager
Other Supported Platforms
Quick reference guides for the remaining 6 advertising platforms.
๐ Google Ads
Quick Facts
- Click ID: gclid (Google Click ID)
- Authentication: OAuth 2.0 with refresh token
- Test Mode: Import test conversions available
- Attribution Window: Up to 93 days
Prerequisites
1 Access Google Ads API Center
Log in to Google Ads and navigate to Tools & Settings โ Setup โ API Center
2 Find Your Customer ID
Your Customer ID is displayed at the top right of the Google Ads interface
Format:
XXX-XXX-XXXX
Example: 123-456-7890
3 Create Conversion Action
Go to Tools & Settings โ Measurement โ Conversions โ Click New Conversion Action โ Select Import โ Choose API
โ ๏ธ Important
Note the Conversion Action ID - you'll need this for configuration
4 Generate OAuth Credentials
- Go to Google Cloud Console
- Create a new project or select existing project
- Enable Google Ads API
- Create OAuth 2.0 credentials (Client ID & Secret)
- Generate refresh token with appropriate scopes
- Request Developer Token from API Center
5 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select Google Ads from dropdown
- Enter Customer ID (format: XXX-XXX-XXXX)
- Enter Conversion Action ID
- Paste OAuth Client ID and Client Secret
- Paste Refresh Token
- Enter Developer Token
- Click Save Configuration
โ Success!
You should see: "Successfully connected to Google Ads"
Troubleshooting
"Invalid Customer ID" Error
Cause: Customer ID format incorrect or missing dashes
Solution: Ensure format is XXX-XXX-XXXX (10 digits with dashes)
Check: Copy directly from top right of Google Ads interface
"Developer Token Not Approved" Error
Cause: Developer token pending approval or invalid
Solution: Request developer token approval in API Center
Check: Allow 24-48 hours for Google approval process
"GCLID Not Captured" Error
Cause: Auto-tagging disabled in Google Ads
Solution: Go to Settings โ Account Settings โ Enable auto-tagging
Check: Verify URLs contain gclid parameter after clicking ads
๐ต TikTok
Quick Facts
- Click ID: ttclid (TikTok Click ID)
- Authentication: Access Token
- Test Mode: Test event codes supported
- Events Supported: 13 standard event types
Prerequisites
1 Access TikTok Events Manager
Log in to TikTok Ads Manager โ Navigate to Assets โ Events โ Web Events
2 Find Your Pixel Code
Click on your pixel, then find the Pixel Code at the top of the page
Format:
C11AAA1AA1AAA1AAAAA1AA
Example: C4B2C8D1E9F3G5H7I9J1
3 Generate Access Token
In the same pixel view, navigate to Settings โ Generate Access Token or go to Developer Tools section
โ ๏ธ Important
Save the access token securely - you won't be able to view it again!
4 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select TikTok from dropdown
- Paste your Access Token
- Enable Conversions toggle
- Paste your Pixel Code
- (Optional) Add Test Event Code for testing
- Click Save Configuration
5 Test Your Connection
Click Test Connection to validate your setup
โ Success!
You should see: "Successfully connected to TikTok Events API"
Troubleshooting
"Invalid Access Token" Error
Cause: Access token expired or has insufficient permissions
Solution: Generate a new access token with Events API permissions
Check: Ensure token is at least 50 characters with no spaces
"Pixel Code Not Found" Error
Cause: Pixel code format incorrect or doesn't exist
Solution: Copy pixel code exactly as shown in TikTok Ads Manager
Check: Verify pixel code is 22 characters (format: C11AAA1AA1AAA1AAAAA1AA)
"Events Not Appearing" Issue
Cause: Events may take 5-15 minutes to appear in TikTok
Solution: Wait for processing, then check Test Events tab
Check: Verify ttclid is being captured from TikTok ad URLs
๐ Pinterest
Quick Facts
- Click ID: epik (Pinterest Click ID)
- Authentication: Access Token
- Test Mode: Available for validation
- Deduplication: 7-day window with event_id
Prerequisites
1 Access Pinterest Ads Manager
Log in to Pinterest Ads Manager โ Navigate to Ads โ Conversions
2 Find Your Pinterest Tag ID
Click on your Pinterest Tag in the Conversions section. The Tag ID is displayed at the top
Format:
2612345678901
13-digit numeric ID
3 Generate Access Token
Go to Business Hub โ Settings โ API โ Click Generate Access Token
โ ๏ธ Important
Copy the access token immediately - Pinterest won't show it again!
4 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select Pinterest from dropdown
- Paste your Access Token
- Enable Conversions toggle
- Enter your Tag ID
- Enter your Ad Account ID (optional but recommended)
- Click Save Configuration
5 Test Your Connection
Click Test Connection to verify your credentials
โ Success!
You should see: "Successfully connected to Pinterest Conversions API"
Troubleshooting
"Invalid Access Token" Error
Cause: Access token expired or has insufficient permissions
Solution: Generate a new access token with Conversions API permissions
Check: Ensure token starts with "pina_" and is at least 60 characters
"Tag ID Not Found" Error
Cause: Tag ID doesn't exist or account doesn't have access
Solution: Verify Tag ID is exactly 13 digits (no letters or spaces)
Check: Confirm tag exists in Pinterest Ads Manager โ Conversions
"Events Not Showing" Issue
Cause: Processing delay (Pinterest can take up to 24 hours)
Solution: Wait for processing, verify epik is being captured
Check: Ensure Pinterest Tag is installed and firing on your website
๐ค Reddit
Quick Facts
- Click ID: rdt_cid (Reddit Click ID)
- Authentication: OAuth 2.0 Client Credentials
- Test Mode: Sandbox environment available
- Attribution Window: Configurable (7-30 days typical)
Prerequisites
1 Access Reddit Ads Manager
Log in to Reddit Ads โ Navigate to Events Manager
2 Find Your Pixel ID
In Events Manager, click on your pixel. The Pixel ID is at the top of the pixel settings
Format:
t2_abc123def
Starts with "t2_" followed by alphanumeric characters
3 Generate API Credentials
Navigate to Pixel Settings โ API Access โ Click Generate Credentials. You'll receive a Client ID and Client Secret
โ ๏ธ Important
Save both Client ID and Client Secret immediately - the secret cannot be retrieved later!
4 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select Reddit from dropdown
- Paste your Client ID
- Paste your Client Secret
- Enable Conversions toggle
- Enter your Pixel ID (format: t2_abc123def)
- Click Save Configuration
5 Test Your Connection
Click Test Connection to verify OAuth authentication
โ Success!
You should see: "Successfully authenticated with Reddit Conversions API"
Troubleshooting
"Authentication Failed" Error
Cause: Client ID or Client Secret incorrect or expired
Solution: Regenerate API credentials in Reddit Ads Manager
Check: Ensure credentials have Conversions API permissions
"Pixel Not Found" Error
Cause: Pixel ID format incorrect or doesn't exist
Solution: Verify Pixel ID starts with "t2_" and matches exactly
Check: Confirm pixel exists in Reddit Events Manager
"Events Not Showing" Issue
Cause: Events may take 1-3 hours to appear in Reddit reporting
Solution: Wait for processing, verify rdt_cid is being captured
Check: Ensure Reddit Pixel is installed and active on your website
๐ฆ Twitter / X
Quick Facts
- Click ID: twclid (Twitter Click ID)
- Authentication: OAuth 1.0a (4 credentials required)
- Test Mode: Available for validation
- Attribution Window: 30 days for conversions
Prerequisites
1 Access X Developer Portal
Log in to X Developer Portal โ Create or select your app โ Navigate to Keys and Tokens
2 Generate OAuth 1.0a Credentials
In Keys and Tokens, generate all four OAuth 1.0a credentials
Required credentials:
- โข Consumer Key (API Key)
- โข Consumer Secret (API Secret)
- โข Access Token
- โข Access Token Secret
3 Find Your Pixel ID
Go to X Ads Manager โ Tools โ Events Manager. Your Pixel ID is at the top of the pixel settings
โ ๏ธ Important
Save all credentials securely - tokens cannot be retrieved later!
4 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select Twitter/X from dropdown
- Paste your Consumer Key (API Key)
- Paste your Consumer Secret (API Secret)
- Paste your Access Token
- Paste your Access Token Secret
- Enable Conversions toggle
- Enter your Pixel ID
- Enter your X Ads Account ID
- Click Save Configuration
5 Test Your Connection
Click Test Connection to verify OAuth 1.0a authentication
โ Success!
You should see: "Successfully authenticated with X Ads API"
Troubleshooting
"OAuth Signature Invalid" Error
Cause: One or more OAuth 1.0a credentials incorrect
Solution: Verify all 4 credentials (Consumer Key/Secret, Access Token/Secret)
Check: Regenerate credentials if any are expired or revoked
"Insufficient Permissions" Error
Cause: Access token doesn't have AD_MANAGER permissions
Solution: Ensure app has AD_MANAGER or ACCOUNT_ADMIN permissions
Check: Verify permissions in X Developer Portal app settings
"Events Not Showing" Issue
Cause: Processing delay (X can take 24-48 hours for reporting)
Solution: Wait for processing, verify twclid is being captured
Check: Confirm auto-tagging is enabled in X Ads campaign settings
๐ Bing Ads (Microsoft Advertising)
Quick Facts
- Click ID: msclkid (Microsoft Click ID)
- Authentication: OAuth 2.0 with refresh token
- Test Mode: Test conversions supported
- API: Offline Conversions API for enhanced tracking
Prerequisites
1 Create Azure AD Application
Log in to Azure Portal โ Azure Active Directory โ App Registrations โ New Registration. Grant "Microsoft Advertising" API permissions
2 Generate OAuth Credentials
In your Azure AD app, navigate to Certificates & Secrets โ Create client secret. Then configure redirect URI for OAuth flow
Required credentials:
- โข Client ID (Application ID)
- โข Client Secret
- โข Refresh Token (from OAuth flow)
3 Find Account & Goal IDs
Go to Microsoft Advertising โ Tools โ Conversion Tracking โ Offline Conversion Goals. Note your Customer ID, Account ID, and Conversion Goal ID
โ ๏ธ Important
Create an Offline Conversion Goal first - this is required for API tracking
4 Configure in Tandem Beam
- Return to Platform Configurations
- Click Add New Configuration
- Select Bing Ads from dropdown
- Enter your Customer ID
- Enter your Account ID
- Enter your Conversion Goal ID
- Paste your OAuth Client ID
- Paste your OAuth Client Secret
- Paste your OAuth Refresh Token
- Click Save Configuration
5 Test Your Connection
Click Test Connection to verify OAuth and API access
โ Success!
You should see: "Successfully connected to Bing Ads API"
Troubleshooting
"OAuth Token Expired" Error
Cause: Refresh token expired or revoked
Solution: Complete OAuth flow again to generate new refresh token
Check: Verify Azure AD app has Microsoft Advertising API permissions
"Conversion Goal Not Found" Error
Cause: Offline Conversion Goal ID incorrect or inactive
Solution: Verify Goal ID in Microsoft Advertising โ Conversion Tracking
Check: Ensure goal type is "Offline Conversion"
"MSCLKID Not Captured" Issue
Cause: UET Tag not installed or auto-tagging disabled
Solution: Install UET Tag and enable auto-tagging in campaign settings
Check: Verify msclkid parameter appears in URLs from Bing ads
๐งช DEV+NULL Testing Platform
Quick Facts
- Purpose: Safe testing destination (no real data sent to ad platforms)
- Authentication: None required (internal testing)
- Test Mode: Always active
- Best For: Validating tracking setup before connecting real platforms
What is DEV+NULL?
DEV+NULL is a special testing platform that captures your transformed event payloads without sending data to external advertising platforms. It's perfect for validating your tracking configuration, testing event mappings, and inspecting data transformations in a completely safe environment.
โ Benefits
- โข Zero risk - no real data sent anywhere
- โข Inspect complete transformed payloads
- โข Test event mappings and configurations
- โข Validate PII hashing works correctly
- โข Debug platform adapter issues safely
๐ฏ Use Cases
- โข Testing new event configurations
- โข Validating conversion tracking setup
- โข Training and onboarding
- โข Debugging attribution issues
- โข Pre-production validation
1 Add DEV+NULL Platform
Go to Platform Configurations โ Add New Configuration โ Select DEV+NULL from the dropdown
2 Optional: Add Label
Provide a display label to identify this test destination (completely optional)
Example labels:
- โข "Testing Setup"
- โข "QA Environment"
- โข "Training Sandbox"
3 Save Configuration
Click Save Configuration. DEV+NULL is immediately ready - no credentials or testing needed!
4 Configure Event Settings
In your Event Settings, include DEV+NULL as a destination platform to start capturing test events
5 Send Test Events & Inspect
Trigger events on your website, then inspect captured payloads in the Attribution Dashboard
โ What You'll See
Events show "DEV+NULL" as platform with complete request/transformed payloads for inspection
โ ๏ธ Testing Platform Only
DEV+NULL does not send data to external advertising platforms. Use it for testing and validation only. When you're ready for production conversion tracking, configure real platforms (Meta, Google Ads, LinkedIn, etc.) using the guides above.
What Can I Test?
Event Tracking
- โข Verify events are being captured
- โข Confirm event names are correct
- โข Check event parameters and values
- โข Validate timing and sequencing
Data Transformation
- โข Inspect platform-specific transformations
- โข Verify PII hashing (SHA-256)
- โข Check click ID capture and attribution
- โข Validate custom event mappings
Advanced: Inspecting Payloads
Captured events are stored and can be inspected to verify your tracking configuration. Each captured event includes:
- โข Request Payload: Original event data as received by Tandem Beam
- โข Transformed Payload: Data after platform-specific transformations
- โข Metadata: Vendor IDs, tandem tracking, adapter configuration
- โข Headers: HTTP headers for debugging
- โข Trace ID: Links to full event trace in Attribution Dashboard
Common Issues & Solutions
"Connection Timeout" Error
Cause: Network issues or platform API temporarily unavailable
Solution: Wait 5-10 minutes and try again. Check platform status pages for outages.
"Test Failed" Error
Cause: Credentials saved but test event couldn't be sent
Solution: Configuration is saved. Check platform for test event delivery. May need to whitelist Tandem Beam IPs.
"Rate Limit Exceeded" Error
Cause: Too many API requests in short time period
Solution: Tandem Beam will automatically retry after cooldown. No action needed.
Need More Help?
Contact support with your advertiser ID and platform name for personalized assistance. Include error message if available.
Frequently Asked Questions
Do I need developer accounts for every platform?
Not always. GA4 and Bing Ads work with standard accounts. Meta, Google Ads, and LinkedIn require Business Manager or developer account access for API credentials.
Can I test without sending real data to platforms?
Yes! Meta and TikTok support test event codes. GA4 has a debug endpoint. All platforms can use Tandem Beam's test mode to validate setup without real conversions.
How do I know if platform integration is working?
- Use the "Test Connection" button after configuring
- Check the Attribution Dashboard for platform event delivery
- Verify events appear in the platform's UI (e.g., Meta Events Manager)
- Monitor the Intelligence Dashboard for successful conversions
What if I need to change my credentials later?
Simply edit the platform configuration, paste new credentials, and save. Tandem Beam will automatically use the updated credentials for all future events.
Can I connect multiple platforms simultaneously?
Absolutely! Configure as many platforms as needed. Tandem Beam automatically sends each event to all connected and active platforms with proper attribution.
Which platform should I start with?
For B2C: Start with GA4 (easiest) and Meta (most common).
For B2B: Start with GA4 and LinkedIn.
For E-commerce: Start with GA4, Meta, and Google Ads for comprehensive coverage.
What happens if I enter incorrect credentials?
The "Test Connection" button will show an error message. Your configuration will be saved, but events won't be sent until you correct the credentials. Simply edit the platform configuration and update with correct values.
Do access tokens expire?
It depends on the platform. GA4 API secrets don't expire. Meta tokens can be set to never expire. Google Ads and LinkedIn use OAuth refresh tokens that automatically renew. If a token expires, you'll see authentication errors and need to regenerate.
How long does it take for events to appear in platforms?
Most platforms process events in near real-time (within 1-5 minutes). Some platforms like GA4 may take 15-30 minutes to show events in their UI. Check your Attribution Dashboard in Tandem Beam for immediate confirmation of successful delivery.
Can I pause event delivery to a specific platform?
Yes! Each platform configuration has a "Processing Enabled" toggle. When disabled, Tandem Beam will stop sending events to that platform while continuing to send to all other active platforms. This is useful during platform maintenance or API issues.
What if my platform isn't listed?
Tandem Beam currently supports 9 major advertising platforms. If you need integration with a platform not listed, contact support with your requirements. We regularly add new platform integrations based on customer demand.
Do I need ClickBeam or SkyBeam installed first?
No. Platform configurations are independent of tracking method. You can configure platforms first, then deploy ClickBeam or SkyBeam later. However, events will only be sent to platforms after tracking is active on your website.
What data does Tandem Beam send to platforms?
Tandem Beam sends conversion events (purchases, leads, sign-ups) along with hashed user data (email, phone), click IDs for attribution, conversion values, and standard event parameters. All personally identifiable information (PII) is automatically hashed using SHA-256 before sending.
How secure are my platform credentials?
Very secure. Tandem Beam encrypts all credentials at rest in the database. Access tokens are never exposed in logs or user interfaces. API communication uses HTTPS exclusively. We follow industry best practices for credential storage and transmission.
Can I use different credentials for different advertisers?
Yes! Each advertiser account can have its own platform configurations with unique credentials. This is perfect for agencies managing multiple clients - each client can use their own Meta Pixel, GA4 property, etc.
What's the difference between "Active" and "Processing Enabled"?
Active means the platform configuration exists and credentials are valid. Processing Enabled controls whether events are actually sent. A platform can be Active but have Processing Disabled (useful for temporary pauses during maintenance).
How do I troubleshoot "Connection Successful but No Events" issue?
- Verify ClickBeam or SkyBeam is deployed and active
- Check that Event Settings are configured for your events
- Ensure the platform is included in Event Settings destinations
- Verify "Processing Enabled" toggle is on
- Check Attribution Dashboard for event processing logs
What browsers are supported for tracking?
ClickBeam supports all modern browsers (Chrome, Firefox, Safari, Edge) and mobile browsers (iOS Safari, Chrome Mobile). SkyBeam works at the server level so browser compatibility is not a factor. Both tracking methods work on all devices.
Can I track conversions that happen offline?
Yes! Most platforms support offline conversions. GA4 accepts events up to 72 hours after they occur. Meta, Google Ads, and LinkedIn all support offline conversion imports. Tandem Beam handles the technical details - you just send the conversion event whenever it happens.
How does Tandem Beam prevent duplicate conversions?
Each event gets a unique event ID that platforms use for deduplication. If the same conversion is tracked by both your platform pixel and Tandem Beam, the platforms automatically deduplicate based on the event ID, click ID, or transaction ID depending on the platform.
Ready to Connect Your Platforms?
Head to Platform Configurations to start setting up your integrations. Begin with GA4 for the quickest setup.
Go to Platform Configurations โ