Bulk event sending
How to think about bulk or manual event sending in Axalot without breaking attribution, optimization, or reports.
Console path
Console / Tracker / PostbacksConsole / Tracker / Reports
When bulk sending is useful
Bulk event sending is useful for controlled operational cases:
- Replaying events after a temporary destination outage.
- Sending missed events after a verified integration issue.
- QA testing a destination with known click ids.
- Backfilling a small, audited batch.
Safety rules
| Rule | Reason |
|---|---|
| Use known click ids | Events without attribution are not useful. |
| Keep batches small | Large retries can create duplicate optimization signals. |
| Document the reason | Future report readers need context. |
| Avoid low-quality statuses | Do not send declined/trash events to optimization pixels unless intentional. |
Bulk sending can distort reports
Treat bulk sending as an operational repair tool, not a normal traffic workflow.
Related pages
Pixels and outgoing callbacks
How Axalot sends matched conversion and funnel events to Facebook, HTTP GET endpoints, Telegram Bot callbacks, and stream-level pixel destinations.
Facebook Pixel and CAPI
How Facebook outgoing events are configured in Axalot with pixel selection, event mapping, and stream-level delivery.