Skip to content
Random Truffle
THE RT ECOSYSTEM

Your world.
Working together.

The value is not the number of tools. It is the context that survives as work moves between them.

A persistent context packet carries objective, audience, evidence, creative, measurement and memory. Permissions are scoped to each destination.

Signals in.
Understanding throughout.
Action with context.

The same audience strategy can inform many destinations. The method of getting there remains specific to each platform.

Explore the Data Foundation →
01 / SIGNALS

Read the situation.

Behavior, relationships, transactions, research and campaign response establish the question.

02 / FOUNDATION

Agree on the context.

The marketing data lake in your BigQuery keeps identity, definitions, permissions and history together.

03 / ACTIVATION & OWNED CHANNELS

Adapt the next move.

Choose a supported activation method, format and measurement approach for each destination.

ONE DIRECTORY

Where your context
connects.

The role each platform can play in a connected marketing workflow. A platform can play more than one role. What is available to you depends on your implementation and on each platform’s requirements.

Showing 9 of 35 integrations

Google Analytics logo

Google Analytics

  • Signals

Understand on-site and in-app behavior.

Explore its role
Context it can contribute
Permitted events, sessions and defined conversion actions.
Why it matters
Explore the path between discovery, repeated consideration and conversion.
What needs validation
Event definitions, export availability, freshness and eligible identifiers must be checked.
See Nexus in action →
Shopify logo

Shopify

  • Signals

Connect intent to the transaction.

Explore its role
Context it can contribute
Orders, product catalog context, returns and customer account keys.
Why it matters
Distinguish a first purchase from a repeat purchase using consistent definitions.
What needs validation
Deduplicate order IDs and specify refunds, currency and reporting windows.
See Nexus in action →
Google BigQuery logo

Google BigQuery

  • Foundation

Where the Data Foundation lives: the marketing data lake in your own environment.

Explore its role
Context it can contribute
Customer, sales, campaign, audience, creative and response data brought into one marketing schema.
Why it matters
Give every agent the same definitions, history and campaign memory, in a cloud you own.
What needs validation
Projects, access, refresh cadence and costs are set in each deployment.
See Nexus in action →
Google Cloud logo

Google Cloud

  • Foundation

The cloud environment that hosts the foundation.

Explore its role
Context it can contribute
Cloud infrastructure and data services selected for the implementation.
Why it matters
Host the processing and context layers that support coordinated agent workflows.
What needs validation
Infrastructure choices and production controls are defined in each deployment.
See Aura in action →
Google Ads logo

Google Ads

  • Activation
  • Signals

Meet expressed intent, and bring campaign response back.

Explore its role
Context it can contribute
Eligible audience strategy, search intent, creative and a reviewed media plan.
Why it matters
Coordinate search with the same context used by other channels.
What needs validation
Account access, audience eligibility and placement-specific requirements must be validated.
See Radian in action →
Meta logo

Meta

  • Activation

Bring a relevant idea into the feed.

Explore its role
Context it can contribute
Audience brief, image or video direction, exclusions and measurement plan.
Why it matters
Adapt the creative expression while retaining the underlying hypothesis.
What needs validation
Supported audience methods and account permissions must be established separately.
See Prism in action →
Amazon Ads logo

Amazon Ads

  • Activation

Connect the message to a buying moment in retail media.

Explore its role
Context it can contribute
Product context, availability, retail strategy and supported audience methods.
Why it matters
Coordinate retail discovery with search, social and owned-channel planning.
What needs validation
Retail inventory, placement access and reporting windows differ by account and environment.
See Radian in action →
Mailchimp logo

Mailchimp

  • Owned Channels

Continue a permissioned relationship by email.

Explore its role
Context it can contribute
An eligible contact segment, suppression rules and a relevant invitation.
Why it matters
Connect a returning customer’s context to the next useful message.
What needs validation
Contact permission, unsubscribe handling and delivery costs need explicit treatment.
See Radian in action →
WhatsApp logo

WhatsApp

  • Owned Channels

Make the next step conversational.

Explore its role
Context it can contribute
A permitted contact strategy and channel-appropriate message flow.
Why it matters
Carry audience context into a direct conversation when the channel is suitable.
What needs validation
Channel opt-in, supported messaging methods and operational handling must be configured.
See Radian in action →

Logos identify platforms; they do not indicate a partnership, certification or production support. Availability for each platform is pending internal validation and depends on your implementation. Audience activation depends on each platform’s supported methods, permissions and eligibility. Product names and logos are trademarks of their respective owners.

ONE STRATEGY / DIFFERENT METHODS

Shared intelligence.
Specific activation.

Carry one audience strategy across destinations, using the eligibility rules, identifiers, workflows and reporting context each one supports.

RT connects the strategy across those differences: who the work is for, what the message is meant to change and how the response will be interpreted.

Before activationInspect permissions, identifiers, suppression rules and the freshness of the audience definition.
At the destinationValidate the supported method, asset format, account access and delivery constraints.
After responseKeep platform reporting windows distinct from experimental outcomes and business totals.

Start with one workflow.

Choose a business question, identify the necessary sources and define one measurable destination. Add complexity only when it helps the decision.

Find a solution →