Marin Software
Deprecated. Marin’s tracking endpoint cannot be delivered to server to server. This integration is hidden from new installs; an integration already installed on it keeps its revision and keeps delivering. Nothing is removed.
Not deliverable. The Marin Tracker host, tracker.marinsm.com, answers every request (the /tp conversion pixel and the tracker scripts alike) with a redirect to www.marinsoftware.com, checked on 2026-09-22, so no conversion can be recorded. Marin Software went through Chapter 11 in 2025 and publishes no replacement endpoint. Every event in the Marin blueprint is disabled; the entry stays in the catalogue so an existing installation is still visible. The rest of this page describes the reviewed request, which can be switched back on if Marin confirms a working tracker.
The integration was built to send conversions to Marin Software server-to-server through the Marin Tracker conversion pixel (act=2), with the order and item rows Marin uses for revenue attribution.
Prerequisites
Find your client tracking ID
The cid value is in your Marin Tracker snippet.
Note your conversion types
Each item row carries a Marin conversion type ID (case-sensitive). Set the purchase type and, for leads, the lead type.
Collect the Marin UUID
Marin stitches the conversion to the click by the _msuuid cookie set by the Marin click snippet on your landing pages. Add an ID provider that reads it into collected_ids.marin_uuid.
Configure in Signal
Configuration Fields
| Field | Required | Description |
|---|---|---|
client_tracking_id | Yes | Your Marin client tracking ID — the static alphanumeric value unique to your Marin client account, used as the cid parameter and in the Marin Tracker snippet path. Find it in your Marin Tracker deployment snippet or ask your Marin platform representative. |
conv_type_id | Yes | The Marin conversion type ID for purchases (convType in each UTM:I row). Required and case-sensitive: it must exactly match a conversion type configured in your Marin account. |
lead_conv_type_id | No | The Marin conversion type ID for leads, sign-ups and completed quotes. Case-sensitive, must match a conversion type in your Marin account. Lead events are not sent until it is set. |
Management UI Setup
- Go to Integrations > Add Integration > Marin Software.
- Choose a preset: Default (
default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance). - Fill in the fields above and click Save.
Request format
A GET. trans holds one UTM:T transaction row (order ID, affiliation, total, tax, shipping) and one UTM:I row per item (order ID, conversion type, product, category, price, quantity), separated by a newline.
GET https://tracker.marinsm.com/tp?act=2&cid={client_tracking_id}¤cy=GBP&mu=msuuid-123&trans=UTM%3AT%7CORD-1001%7CWeb+Store%7C259.99%7C40%7C5%7C%7C%7C%0AUTM%3AI%7CORD-1001%7CPurchase%7CParka%7CJackets%7C120%7C2%0AUTM%3AI%7CORD-1001%7CPurchase%7CGloves%7CAccessories%7C19.99%7C1Event Mapping
| Signal event | Vendor event | Presets |
|---|---|---|
purchase | 2 | Default, Retail, Insurance |
generate_lead | 2 | Default, Lead Generation, Insurance |
sign_up | 2 | Lead Generation |
quote_completed | 2 | Insurance |
Identity
The Marin UUID is sent as mu. That parameter name is not in Marin’s public documentation; confirm it with Marin on a live account. The visitor’s IP address and user agent are sent as request headers. No personal data is sent.
Consent
Marin Software is an advertising destination and requires marketing consent by default.
Known limitations
- Not deliverable: the tracker host redirects every request to Marin’s home page, so the events are disabled.
- The Marin UUID parameter name (
mu) needs confirming with Marin.
Troubleshooting
| Problem | Solution |
|---|---|
| Lead events dropped in Signal | Set the Lead Conversion Type ID. |
Blueprint
The Marin Software blueprint version is 0.4.1. It was last reviewed against the vendor’s documentation on 2026-09-22 and independently verified the same day.