Custom Conversion Names

Learn how to use custom conversion names in AnyTrack, including naming rules, platform mapping, and proper syntax.

Standard events don't capture every conversion that matters to your business. When customers hit your "Download Trial" button, complete a quiz, or reach a specific funnel step, those actions drive revenue—but Lead and Purchase don't tell the full story. Custom conversion names let you track exactly what matters, build audiences around specific micro-conversions, and optimize campaigns for the actions that actually predict revenue.

Custom events work like standard events—same attributes, same server-side delivery, same Event Match Quality benefits—but you control the naming. Track trial_download_complete, quiz_submitted, or demo_booking_confirmed instead of generic events that don't reflect your funnel reality.

🚧

TL;DR about Custom Conversion Names

  1. Anytrack supports custom event names.

  2. Custom event names can be sent via JS snippet or via Server Side integration

  • Allowed characters:
    • letters (A-Z, a-z),
    • digits (0-9),
    • underscores (_), hyphens (-), parentheses (()), periods (.), colons (:), equal signs (=), and spaces.
  • Disallowed characters: anything outside the set above is stripped automatically—no emojis, quotes, slashes, etc.
  • Whitespace handling: leading and trailing spaces are removed.
  • Length cap: event names are truncated to the first 40 characters.

What Are Custom Conversion Names?

Custom events are powerful because they allow you to send exactly the conversion signals that matter to your business. They are ideal when:

  • You have your own funnel or business rules
  • Standard events don’t cover your use case
  • You want to segment data based on highly specific actions

These events behave just like standard conversion names within AnyTrack, and all standard event attributes are supported.

⚠️

Important:

You must ensure these events are correctly mapped to your Ads platform's conversion events. Otherwise, they won’t be recognized and optimized by your ad networks.


How to Use Custom Conversion Names in Ads Platforms

To ensure compatibility, use the appropriate conversion category and naming conventions in:

  • Google Ads: Match your custom event to a conversion action set up in Google Ads (e.g., signup_form, purchase_confirmed)
  • Meta (Facebook Ads): Map your custom event under a custom conversion or standard event name in Events Manager

Incorrect or unmapped event names will result in dropped conversions or loss of attribution.


Rules and syntax for Custom Conversion names

✅ Allowed Syntax

  1. Max 40 characters

    • If your event name exceeds this limit, it will be trimmed to the first 40 characters.
  2. Allowed characters

    • Letters (A–Z, a–z)
    • Numbers (0–9)
    • Symbols: - _ * ( ) . : =
❗️

Warning:

Any other characters will be automatically removed from the event name.

Example

Input:

AnyTrack('trigger', 'signup_complete@PRO!version#3🔥🔥🔥', {
  email: '[email protected]',
});

Normalized Result:

signup_completePROversion3

And trimmed to 40 characters if necessary.


Sample Event Snippets

Use the following format to send a custom conversion event:

AnyTrack('trigger', 'custom_event_name', {
  eventValue: 100,
  currency: "USD",
  email: "[email protected]"
});

Examples:

AnyTrack('trigger', 'premium_checkout_started', {
  eventValue: 49.99,
  currency: "USD",
  email: "[email protected]"
});
AnyTrack('trigger', 'webinar_signup_bonus', {
  email: "[email protected]",
  name: "Jane Doe",
  funnel_step: "registration_page"
});