AdsPing

Test Event Code

Per-pipeline test mode. Route AdsPing events to the platform's Test Events tab so you can verify integration without polluting production reporting.

What it is

Each pipeline can carry an optional test_event_code that AdsPing merges into every outgoing event. Platforms recognize the code and route events to a separate "Test Events" stream instead of counting them as production conversions.

Use this whenever you want to verify a destination is wired correctly without firing fake conversions into your real ad attribution data.

Platform support

PlatformTest modeWhere to find the code
Meta CAPI✓ Test Events tabEvents Manager → pixel → Test Events → top of page
TikTok Events API✓ Test Events tabAds Manager → Tools → Events → pixel → Test Events
GA4✓ DebugView (uses debug_mode flag, not test code)GA4 → Reports → Realtime → DebugView
Google Ads✗ No real-time test streamUse Diagnostics tab + a separate test conversion action

Set a test code

  1. AdsPing dashboard → pixel detail → scroll to Pipelines section.
  2. Click the pencil icon next to the pipeline you want to test (Meta CAPI, TikTok Events).
  3. Paste the test code (e.g. TEST12345 for Meta, TEST_ABCDEFGH for TikTok) into the Test Event Code field.
  4. Save.
  5. The pipeline row gets an orange "Test mode" badge in the list — visual confirmation that it's diverted.
Test mode is per-pipeline. Setting a code on the Meta pipeline doesn't affect TikTok. To test all destinations at once, set codes on each pipeline individually.

Verify in the platform

Meta

  • Trigger an event on your site (refresh the page, submit a form).
  • Meta Events Manager → your pixel → Test Events tab. The event appears within 2 seconds.
  • You'll see source = "Server" and the full payload (event_id, user_data, custom_data).

TikTok

  • Trigger an event on your site.
  • TikTok Ads Manager → Tools → Events → pixel → Test Events. The event appears within 2-5 seconds.
  • Source column shows Server for AdsPing-forwarded events. If the browser pixel is also active you'll see Both with a "Deduplicated" tag.

Clearing test mode

  1. Open the same pipeline edit dialog.
  2. Clear the Test Event Code field (delete all characters).
  3. Save.
  4. The orange "Test mode" badge disappears. Next event flows to production reporting.
Forgetting to clear the test code is a common gotcha. The badge in the pipeline list is there specifically to make this hard to miss.
PreviousManual setupNextVerifying setup