Skip to content
Realvertising

By Getelis Ltd

← All integrations

Developer

Post the outcome that matters. Read back where it went.

Most businesses hold at least one outcome no standard connector covers. Realvertising takes it directly: event type, timestamp, value, currency, whichever identifiers you can supply, and an idempotency key you choose. A restatement replaces the original outcome instead of creating a second one, so a corrected value never double-counts. Each event returns a receipt, and each forwarded event returns the network, the conversion action and the status it was accepted under.

In short: A signed HTTP endpoint takes the outcomes only your systems know — a qualified demo, an activated account, a contract signed offline, a delivered order, a value your stack computes — with identifiers, a value and an idempotency key. Realvertising forwards them to the networks and returns a receipt and a delivery trace for every event.

Start free

What it is

A signed HTTP endpoint accepts the outcomes your own systems own: a qualified demo, an activated account, a contract signed offline, a delivered order, a value computed in your stack. Every event carries identifiers, a value and an idempotency key you control.

What Realvertising receives

  • Outcome events with type, timestamp, value, currency and the identifiers you hold — click identifier, hashed email, order reference or your own customer key.
  • An idempotency key per event, so a retried delivery is stored once and a correction replaces the earlier value.
  • Restatements and voids: a refunded order, a cancelled contract, a disqualified lead, with the date the change took effect.
  • Custom dimensions you declare in advance — plan, segment, region, product line — usable for grouping and as Constitution rules.

What it sends back

  • A receipt per event with the stored outcome identifier, the idempotency key it resolved to, and the validation result when one is rejected.
  • A delivery trace: which networks received the outcome, as which conversion action, with what value, and whether each accepted it.
  • Webhooks for every Growth Brain action — budget moved, campaign paused, audience updated, creative rotated — with the evidence and the Constitution rule that permitted it.

What this lets you ask

Questions this connection makes answerable.

  • Did the outcome we posted at 09:14 reach Google and Meta, and with what value?
  • Which of our custom outcomes were rejected this week, and for what reason?
  • What changed overnight, and which Constitution rule allowed each change?

How it connects

  1. 1Declare your event types, their value semantics and their custom dimensions; undeclared fields are rejected at the endpoint rather than stored and puzzled over later.
  2. 2Issue a workspace key, post a test event, and read its receipt and delivery trace end to end before production traffic is switched on.
  3. 3Choose which event types reach which networks and which identifiers may be used — the configured consent state decides that last part, not the endpoint.

Where it stops

  • The value you post is the value used. Realvertising does not recompute or second-guess it, so a wrong value travels to every network the event reaches.
  • Identifiers are usable only where the configured consent state permits activation. An event carrying one that may not be matched is still stored, and the delivery trace shows it was withheld.
  • Late outcomes are only as useful as each network's restatement window allows. Events posted outside that window are recorded here and reported as unsent.

Integrations

Everything the Growth Brain can read.

Web analyticsIndependent journey and conversion truth from your own site — held beside network-reported numbers, never merged into them.CRMQualified leads, pipeline and closed-won outcomes become the signal networks optimise toward — not form fills.Finance systemMoney that actually arrived — payments, subscriptions, refunds — becomes the value networks optimise against.Accounting systemGross margin and contribution, as your accountants define them, become the floor under every budget decision.Content platformAd copy is assembled from claims your content platform already approved, and a lapsed claim stops being used.Brand assetsOnly assets with a live licence and the right usage rights reach a placement, and expiry pulls them back out.Consent platformConfigured consent state decides which identifiers may be activated, enforced at every hand-off to a network.Custom APIYour own outcomes and values, posted with an idempotency key and forwarded to the networks as conversion signals.Google AdsOAuth into your manager account, read the campaign tree, write budgets and targets, return conversions keyed by GCLID.MetaSystem User token, Business Manager discovery, budgets written back, and server-side Conversions API events that deduplicate.TikTokBusiness Center OAuth, campaign sync, Events API server events with dedupe, and budgets written under Constitution limits.LinkedInAd account discovery, campaign and creative sync, Lead Gen Form pull, and CRM stages returned through the Conversions API.Microsoft AdsEntra sign-in, account hierarchy sync, offline conversions keyed on MSCLKID, and writes that respect import-managed campaigns.ShopifyOrders, refunds and payouts arrive as commercial outcomes, keyed by order id so a retried webhook cannot count a sale twice.StripePayments, invoices, subscriptions, refunds and payouts ingested on event id, so a replayed webhook never double-counts.

One goal. Every channel. Real business truth.

Connect your ad accounts, say what a good customer is worth, and let the Growth Brain work the objective inside limits you set.

Start free See how it works

No ad spend commitment · Connect one channel to start · [email protected]