Send AppIn clicks to your own server container
If you already run server-side tagging, AppIn can post to it like any other destination. If you do not, you do not need one.
We do not create a container for you, and you do not need one
This is worth saying plainly, because it is the question everyone asks first.
Server-side tagging is a destination here, not the transport. If you already run a container, give us its URL and we will post each event to it; you decide where it goes from there. If you do not run one, add Meta, TikTok or GA4 directly — a container buys you nothing extra in that case.
Using your own domain for links does not change this. The events are sent from our servers after the click, so your domain needs no container, no DNS record and no certificate.
What you need
- Your container URL
- An authorisation header, if your container requires one
What we post
A JSON body carrying the event name, the event_id, the time, the page the click
happened on, and the click’s context: link, hostname, slug, country, platform and
outcome. Where the visitor arrived with a Meta or TikTok click ID, that travels too.
The mistake people make
Dropping the event_id in the container. If events reach the same pixel both from us
and through your container, that ID is the only thing keeping the platform from
counting them twice. Pass it through on your tag.
Your container must be reachable from the internet
AppIn calls your container from its own servers, so the address you enter has to be a
public one. A private address — localhost, 127.0.0.1, anything in 10.x, 172.16–31.x
or 192.168.x, a link-local 169.254.x, or a name ending .internal — is refused when you
save it, and refused again before each send.
If your container runs inside a private network, put it behind a public hostname with TLS and give AppIn that address instead.