Integration guide
FAQ
Common questions and answers for when events do not appear or keys throw errors.
The questions that come up most often during integration.
Why does a Custom Event not appear in production?
Section titled “Why does a Custom Event not appear in production?”Unlike development, production drops unregistered events and events that disagree with the declaration. That is why an event visible in development can go missing only in production.
Check that the event is declared in abto.events.ts,
and that its required properties, types, and enums match the declaration.
Once the mismatch is corrected, the event is captured again from the next send.
The full rules are in Event design.
Why does a $ name warning appear?
Section titled “Why does a $ name warning appear?”Names that start with $ are reserved for the ABTO system, so a product cannot use them.
The warning means that namespace was entered.
Check whether any event or property name uses $.
Rename it in your product’s language, like checkout_completed,
and never send values such as $tenant_id as Custom Properties.
How do I fix API key errors?
Section titled “How do I fix API key errors?”The two keys belong in different places. Use only the Event Key in the browser; the Calling Key cannot send events.
First check which key the failing request uses. Keep the Calling Key in server environment variables only, and remove it from URL queries, source maps, and client bundles. The Event Key appearing in some request URLs is expected behavior, not a misconfiguration.
Is it a problem if the same event appears twice?
Section titled “Is it a problem if the same event appears twice?”No. A retry after a transient network failure is normal behavior.
The server filters out duplicates, so the same event is never counted twice. If the aggregate really doubled, the call itself ran twice rather than being retried, so check whether the code that sends the event runs more than once.