Integrations
TagPipes + Microsoft Ads
Send your website conversions server-side to your Microsoft Advertising UET tag.
Echo: server-side UET
Echo sends conversion events from your site to your UET tag, server-side.
How you set it up
- In Echo, open Destinations, click Add Destination and choose Microsoft Ads.
- Enter your UET Tag ID. No credential is needed.
| What it sends | One request per event, with the event action, category, value, the Microsoft click ID (msclkid) and an event ID. |
|---|---|
| Limits | Microsoft returns success for any request, so delivery cannot be confirmed from its response. Lens has no Microsoft Ads reporting source. |
| Plan | Included with every Echo plan. Counts as one destination. |
Documentation: Echo destinations
What every Echo destination does
- A per-destination event filter decides which events are sent.
- You choose the consent categories an event needs before it is sent. Global Privacy Control signals and bot traffic are handled per destination.
- Failed sends are retried, then held and replayed automatically.
- There is no "send a test event" button yet, and Echo does not yet compare what it sent with what the platform recorded.
More on the module: Echo product page.
How your data is handled
- Credentials you add are stored in Settings > Security & Access, and you can remove them there at any time.
- Each company sees only the data from the accounts and sources it connected.
Read the Privacy Policy and the Terms of Service.
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.
Send Microsoft Ads your real conversions.
Sign up and add Microsoft Ads as an Echo destination, or ask us for a walkthrough first.
Already have an account? Log in.