Pixels, integrations, and webhooks
Connect webhooks, API workflows, invoice tools, pixels, and external systems without mixing seller workflow docs with API reference.
When to use this guide
Use this section when AtomicPay needs to send events, connect to another tool, generate invoices, or support developer workflows.
Start here
- Complete webhook create and test flow for end-to-end webhook setup and verification.
- Plan, test, and monitor webhooks to choose events, test with the simulator, monitor logs, and debug failed deliveries.
- Complete Notazz integration flow for invoice connection and test sale verification.
- Configure Notazz invoice integration to connect invoice credentials, test mode, tax fields, and product mappings.
- Use API keys safely to decide when API access is needed and protect credentials.
- Add Google Tag Manager on checkout to load GTM containers on product checkout pages.
- Complete GTM on checkout flow for GTM preview and tag verification.
- Add GA4 on checkout to send checkout activity to GA4 measurement IDs.
- Complete GA4 on checkout flow for DebugView and purchase event checks.
- Add Crisp chat on checkout to show live chat for buyers on checkout.
- Connect Zapier or Make with webhooks for no-code automation with webhook catch URLs.
- Secure webhook endpoints before production automations depend on them.
- Troubleshoot Notazz invoice issues when invoice generation fails or status is degraded.
- Developers area overview for API vs help center orientation.
- AtomicPay API Docs for endpoint, authentication, and payload reference.
What integrations control
| Area | Purpose |
|---|---|
| Webhooks | Sends event notifications to external systems. |
| Notazz | Supports invoice generation workflows when configured. |
| API keys | Lets approved systems connect programmatically. |
| Pixels | Tracks checkout activity for ads and attribution. |
| Logs and simulators | Help test and debug automation before launch. |
Typical workflow
- Define the business workflow before choosing a tool.
- Configure the integration in the correct business or product context.
- Test in a low-risk path.
- Review logs, status, or external system output.
- Fix failures before launch traffic depends on the integration.
Good checks before going live
- Keep API keys out of frontend code and public docs.
- Test webhook delivery with the simulator.
- Confirm Notazz tax fields with the seller or finance team.
- Verify pixels before paid traffic starts.
- Keep API-specific setup in AtomicPay API Docs.