Send back the events
worth optimizing for.
Connect the conversions recorded in Skro with your ad platforms. Configure supported server-side integrations, choose the events to send, and map event names around the outcomes that matter to your campaigns.
Start with the Free plan. No credit card required.
Your event. The source’s format.
click_7f2a…- Meta & TikTok event delivery
- Google & Microsoft conversions
- Custom event mappings
Connect with the tools in your workflow
A conversion should inform your next campaign decision.
Your network or store may know a purchase happened before the ad platform does. Skro can receive that event, attribute it to the campaign, and send a supported conversion back through the configured source integration.
Connect the source integration
Configure the traffic source’s supported conversion API and the required pixel, data source, conversion action, or account credentials.
Choose what to send
Use custom conversion settings and source mappings to control outgoing event names and whether an event sends a source postback.
Investigate the delivery
Follow outgoing postback records and integration responses. Check event data and source configuration when the platform does not receive the result you expect.
One internal event. The right name for each source.
Keep a clear event model in Skro while mapping outgoing names to source requirements. Postbacks can carry supported conversion values and additional matching parameters when your setup provides them.
- Meta, TikTok, Google Ads, Microsoft Ads, and SmartNews integrations
- Event-name mappings and controls for custom conversions
- Conversion and outgoing postback logs for troubleshooting
Close the loop from conversion source to ad platform.
- 01
Receive the conversion
Your network, store, or backend sends Skro the click ID and the conversion details.
- 02
Apply your event settings
Skro records the event using your conversion definition, payout settings, and source mappings.
- 03
Deliver to the source
The enabled integration sends supported event data to the ad platform; verify the result in both systems.
Built to be set up.
Guides to get you there.
Follow the workflow for your platform, then test the full path before relying on campaign results.
Which platforms are supported?
Skro has conversion delivery integrations for Meta, TikTok, Google Ads, Microsoft Ads, and SmartNews. Each integration has its own configuration and supported event requirements.
Can I send only selected events?
Yes. Custom conversions have outgoing-postback controls, and traffic-source settings allow you to configure which custom events are sent and how they are named.
Can I send store and call conversions?
Yes, when the event is correctly attributed in Skro and the source integration supports the event data. Follow the relevant store or call-platform guide before enabling delivery.
Does server-side delivery guarantee platform attribution?
No. Delivery and attribution still depend on valid click and matching data, event timing, consent settings, source configuration, and the ad platform’s own requirements.
Put conversion feedback to work.
Connect a supported source, choose your events, and verify the full path from conversion to delivery.