What Slipky does on each ad platform, and what it does not.

Early access means the list below is the real one. If a cell says no, the feature does not exist for that platform yet.

The three platforms side by side

Capability	Meta	Google Ads	TikTok
Connect the ad account with its own sign-in flow	Yes	Yes	Yes
Sync campaigns and daily metrics every hour	Yes	Yes	Yes
Change campaign status from Slipky and confirm it on the platform	Yes	No, saved in Slipky only	No, saved in Slipky only
Send a Purchase event for a Stripe payment	Built, not ready to rely on	No, needs a click id	Built, not ready to rely on
AI ad copy formatted for the platform	Yes	Yes	Yes

The Meta and TikTok send-back code has not run successfully against any ad account, simulated or live, and it passes the ad account id where the platforms expect a pixel or dataset id. Treat it as not working until the founder says it is fixed.

Naming

Meta, Google Ads, TikTok and Stripe are names of services Slipky connects to. Slipky is an independent product of Mazacode LTDA. It is not made, endorsed or approved by any of those companies.

What this means in practice

If you only run Google Ads, Slipky gives you the synced view, alert rules and AI copy, and it will not send revenue back to Google. If you run Meta, you also get status changes that reach the platform. Sending purchases back is not usable for any platform yet. TikTok reads and syncs like the others, and status changes stay local.

Common questions

Why is Google not sent conversions?

Google Ads matches an offline conversion to a click id captured when the visitor clicked the ad. Slipky does not capture click ids yet, so there is nothing to upload, and the event is marked not supported instead of delivered.