Cross-domain tracking for a raise: follow the investment, not the click

Cross-domain tracking matters when a campaign starts on the issuer's site and the investment finishes on an intermediary's site. Without an agreed way to join those records, the issuer sees an ad click and a departure. The intermediary sees an investment. Neither system alone tells the team which campaign produced it.

That pattern is common, but it is not universal. An issuer may send ads directly to a portal-hosted testing-the-waters page that becomes the live offering page. Then there may be no company-site-to-portal page handoff to track. There are still questions about what the intermediary measures, exports, and permits the issuer to use. Choose the page setup first, then design attribution for the path people will actually take.

Draw the path before installing anything

Start with a single real visitor path: ad, landing page, interest form if any, portal page, account creation, investment commitment, and the intermediary's final transaction record after close. Mark who owns each step and where the domain changes. The lead-funnel is useful because a click, reservation, started checkout, active commitment, and final investment are different events. Calling them all “conversions” makes campaign reporting useless.

A new domain does not automatically erase every possible identifier. It does mean the issuer's browser cookie and page script cannot simply observe what happens on the intermediary's site. Privacy controls, session expiration, multiple devices, and the intermediary's own rules create more gaps. Copying a tag to a second site is possible only if that site permits it, and a browser event still is not proof that a subscription was completed.

Carry what the intermediary will accept

Agree on a small set of campaign fields before launch: source, campaign, creative, and a click identifier where applicable. Put them in the link to the intermediary only if the intermediary will receive and preserve them. Test redirects, account creation, email verification, and return visits. A parameter that survives the first page but disappears before confirmation does not solve attribution.

An issuer-owned interest form can assign its own lead ID. That ID may be passed to the intermediary if its system supports it. The issuer should not put private investor information into a public URL. An email address in a query string can leak into browser history, logs, and other services. Use opaque IDs and document how they are matched.

Ask exactly what comes back. Some intermediaries can expose a thank-you-page event, server notification, or export. Others provide only aggregate dashboard figures. The answer affects how precisely a campaign can be optimized. Get it in the contract or implementation plan, not in a sales call.

The confirmation event is the hard part

An investment commitment during a live Reg CF offering is provisional. The investor may cancel under the rule, and a material change may require reconfirmation, as the SEC's intermediary guidance explains. Funds received into escrow do not by themselves make the investment final. Only after the offering closes and the intermediary confirms the final transaction record can the issuer report final completed investments. Name the live event active commitment and keep it separate from final investment. If the intermediary offers a confirmation event, ask whether it fires on commitment, funds received, closing, or another state. Ask how cancellations and reconfirmations update it.

There are three practical ways to get the result:

• A portal-side commitment event. Fast enough for live campaign decisions, if the intermediary permits it and the event fires only at the agreed state. Verify that it does not fire twice on refresh. Label its amount provisional until the close.
• A server notification or postback. The intermediary sends an event to a controlled endpoint after a status change. This can be more reliable than a browser page view, but only if both sides agree on event IDs, retries, consent, and reversal events.
• A periodic export. A file of investment records is slower and may omit marketing source. It can still provide the financial source of truth. Join it to earlier leads only on a permitted, reliable identifier, and mark unmatched records honestly.

None is magic. A person may click on a phone and invest later on a laptop. They may forward the offering to someone else. Privacy choices may prevent a match. A campaign should report “unattributed” rather than force those investments into the last campaign that touched the portal.

Ask before you sign

Give the intermediary a short technical questionnaire. Which query parameters survive every redirect? Can the issuer pass an opaque lead ID? Is there a confirmation event, and exactly when does it fire? Are event IDs stable so duplicates can be removed? What status changes are reported later? What fields are in the export, at what frequency, and for how long after the raise? Who may access the data? Can the issuer test with a nonproduction or reversible transaction?

Ask the technology team who will own the issuer-side endpoint, the matching rules, and the weekly reconciliation. These roles can sit under one contract or several. The point is to name an owner for the gap. The team-behind-a-raise post offers the wider set of role questions.

Prove the path with live test events

Before the first media dollar, follow a tagged test link from a phone. Record its campaign fields and lead ID. Complete the interest step, if there is one. Then use the intermediary's approved test path to reach the event it calls confirmation. Check the issuer's event log, any ad destination, and the intermediary record. Verify timestamps, amount, currency, ID, and state. Refresh the confirmation page and confirm the count does not double. Test a cancellation or failed payment if the intermediary supports it.

Do this again after a portal redesign or a changed account flow. A spreadsheet showing that events were mapped in theory is not evidence that a live visitor's path works.

If the intermediary offers no campaign fields or event access, use its export for the active commitment total during the raise and the final investment total after close. Use the issuer's campaign data as directional evidence. You can compare time periods, creative changes, and cost against provisional active commitments during the campaign, then reconcile to final investments when the offering settles. You cannot honestly claim precise channel-level return where the bridge is absent. Make that limit visible in the dashboard and ask whether another page setup would give the next raise better data.

During the live raise, active commitments are the best available transaction signal, but they can change. Final investments measured by the intermediary after close, net of cancellations and failed reconfirmations, settle the campaign's economics. The attribution bridge helps explain where those investments came from. It does not create them.

FAQ

Why does my tracking stop at the funding portal?

Your site's analytics cannot automatically read events on another organization's domain. The intermediary has to support a shared identifier, a confirmation signal, or an export that can be joined to your records.

Can I put my pixel on the funding portal?

Only if the intermediary permits it. Even then, confirm what the event means and whether consent rules allow it. A page-view pixel is not a verified investment record.

How do I track completed investments?

Define both states with the intermediary: active commitments during the offering and final investments after close. Obtain a portal-side event, server notification, or regular export, then reconcile cancellations, reconfirmations, and duplicates. Treat the intermediary's final transaction ledger as the financial source of truth.

What is a postback?

It is a server-to-server message that a defined event happened, such as an investment status change. It can carry an event ID and campaign identifier without depending on a visitor's browser reaching a thank-you page.

How do I test tracking before launch?

Follow the exact ad link on a phone, complete the approved test flow, and check that the same ID and event state appear once in each system. Test a refresh, a return visit, and a failed or canceled transaction if the intermediary permits it.