Integrations / Advertising
LINE Ads
Server-side conversion tracking via the LINE Conversion API v1. Delivers page views and conversion events (purchase, add to cart, view content, lead, sign-up, search) to LINE Ads with SHA-256 hashed email/phone, the LINE click ID (ldtag_cl), browser_id, and IP/user-agent for identity matching, plus message_id-based deduplication.
Datafly Signal delivers first-party events to LINE Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LINE Ads expects.
Why route LINE Ads through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions LINE Ads optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so LINE Ads receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what LINE Ads needs to attribute the event to the right session.
Click identifiers are captured and replayed
Signal stores click_id first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
One consent decision governs every destination
LINE Ads is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartgenerate_leadpagepurchasesearchsign_upview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the LINE Ads documentation.
Frequently asked questions
Does Datafly Signal integrate with LINE Ads?
Yes. Datafly Signal delivers first-party events to LINE Ads server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload LINE Ads expects. The integration is included in every deployment at no additional cost.
How is server-side LINE Ads tracking different from the LINE Ads tag?
The LINE Ads tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to LINE Ads from your server, so delivery does not depend on browser conditions.
What personal data is sent to LINE Ads?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so LINE Ads receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to LINE Ads?
The blueprint ships with mappings for add_to_cart, generate_lead, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to LINE Ads through pipeline configuration without a code change.
Do I need to keep the LINE Ads tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so LINE Ads deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move LINE Ads server-side?
See how Datafly Signal delivers first-party events to LINE Ads from infrastructure you control, with hashed identity and consent enforcement built in.