Marketing Automation · Integration
Kenshoo
Add Kenshoo to your product for your customers, and give your AI agents governed access to it.
Embed a Kenshoo integration so your customers can manage their own paid media from inside your product rather than in a separate console. Each customer authorises their own account, so campaigns and spend stay on their side and data is delivered per tenant. fastn handles authentication, pagination, and API upkeep, and performance reads are throttled so a large pull does not exhaust a customer's allowance.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own campaigns and ad groups into your product, mapped to their structure.
Create, pause, or update a campaign from an event in your product instead of by hand.
Read performance data such as spend, impressions, and clicks so results appear where users work.
Adjust budgets or bids from your product within limits the customer sets.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads campaign performance before recommending a budget or bid change.
An agent pauses or updates a campaign within governed permissions, with each change logged.
An agent reacts to a spend threshold being crossed and reports what drove it.
Example prompt
Show campaigns whose spend rose more than 20 percent week over week and how their clicks moved.
Set up Kenshoo in 4 steps
- 01Open the Kenshoo connector from your fastn dashboard.
- 02Have each customer authorise their own Kenshoo account.
- 03Map the campaign structure and performance fields your product uses, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Kenshoo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Kenshoo integration without building it. Your customers connect their own Kenshoo account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Kenshoo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Kenshoo connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Google Ads
Marketo
Salesforce Marketing CloudOften used alongside
Tools the same teams tend to run next to Kenshoo, across other categories.
HubSpot
Pipedrive
Zoho CRMKenshoo integration FAQ
How do I add a Kenshoo integration to my product?
Enable the Kenshoo connector in your fastn dashboard, then let each customer authenticate their own Kenshoo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Kenshoo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Kenshoo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Kenshoo account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Kenshoo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads campaign performance before recommending a budget or bid change.
Who maintains the Kenshoo integration?
fastn does. When Kenshoo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger a Kenshoo campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Kenshoo?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Kenshoo integration?
A common starting point: read their own campaigns and ad groups into your product, mapped to their structure. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Kenshoo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Kenshoo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Kenshoo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.