Use Apollo with an AI Browser for Campaign Research

If you use Apollo and you regularly need to research a campaign or partnership before it ships, the bottleneck is usually the same: Apollo holds part of the context, but campaign research also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the Apollo context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles campaign research when Apollo is one of the inputs. It names the Apollo surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a marketer, founder, partnership manager is trying to do

The goal of campaign research is to gather the context needed to brief, target, and de-risk a campaign before spending budget. The success metric is concrete: campaign launches on time, CAC within target, and creative does not need a rewrite mid-flight. That definition matters because it shapes what Apollo needs to contribute to the workflow.

What signals campaign research actually needs

For each signal below, here is whether Apollo can contribute directly or whether Strawberry has to find it via the browser:

• Audience segmentation (who exactly buys this) - Apollo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Competitor messaging already in the space - Apollo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Winning ad examples (Meta Ad Library, LinkedIn) - Apollo stores or surfaces this directly. Strawberry reads it through the connected integration.
• Channel-fit (does the audience even read this channel) - Apollo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Creative reference library - Apollo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Compliance constraints (data, privacy, claims) - Apollo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Apollo

Strawberry can search Apollo by ICP filter, enrich a candidate list with verified emails, and combine that with web research for personalized outreach.

Apollo surfaces Strawberry uses for this workflow: contacts, companies, sequences, lists, filters.

How Strawberry runs campaign research with Apollo

1. Strawberry opens the Apollo contacts that contains the relevant context.
2. The companion pulls related context from Apollo (companies, history, attached files) where it exists.
3. For the parts Apollo does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
4. Strawberry synthesises the output in the shape this workflow needs: A campaign brief.
5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Apollo or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with Apollo connected. Adjust the specifics to your actual ICP, role, or topic.

Read this Apollo contacts and any linked context.
Then run a full campaign research workflow on it. Use the browser to fill any gaps not in Apollo.
Return the output in the shape we use for campaign research: A campaign brief: audience, channels, messaging hypotheses, creative refs, KPIs, risks.
Do not send anything externally. Save the draft to me to review.

What a good campaign research output looks like

Here is what a finished output for campaign research should look like in practice. The specifics will change for your use case, but the shape should look similar:

• Campaign: AI browser launch on Meta Ads - Nordic ICP
• Audience: founders + ops leads at 10-200 person SaaS companies in SE/DK/NO
• Channels: Meta Ads (primary), LinkedIn (secondary), founder LinkedIn organic
• Messaging: 'The browser that does the boring work' - 3 variants
• Risks: Meta still needs Business Verification stable; budget capped at €500/wk in test phase

Why Apollo for this, and where to use a different tool

Apollo is strong for this workflow because Strawberry can search Apollo by ICP filter, enrich a candidate list with verified emails, and combine that with web research for personalized outreach.

Where Apollo falls short Apollo credits are consumed per contact reveal; phone reveal credits are separate; account is shared so usage adds up fast.

Consider also a CRM (HubSpot, Salesforce, Pipedrive) once the prospect enters pipeline.

Common mistakes when running campaign research

• Skipping competitor analysis and rebuilding a positioning someone else already won
• Guessing at audience instead of pulling real segmentation
• No creative references so the team designs in a vacuum

Connecting Apollo to Strawberry

Apollo API key - reveal_phone_number is currently hardcoded true (known bug). Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.

When Apollo + Strawberry is NOT the right fit for campaign research

Skip this setup if any of the following is true:

• You don't actually need Apollo signals. If everything you need lives on the public web, drop the Apollo step and let Strawberry run on URLs alone - it's faster.
• Apollo credits are consumed per contact reveal will block the speed gain.
• The buyer (marketer, founder, partnership manager) doesn't own the decision. If the brief gets handed to someone who'll redo the research, the audit-trail-in-Strawberry advantage is wasted.

3 mistakes that kill this workflow

1. Skipping competitor analysis and rebuilding a positioning someone else already won. Apollo is one input. Strawberry's edge is combining it with everything else. Stop at Apollo-only signals and you'd have been faster with native Apollo reports.
2. Guessing at audience instead of pulling real segmentation. Pre-check Apollo for a recent touch before Strawberry acts on the output. A duplicate hit burns the relationship.
3. No creative references so the team designs in a vacuum. Strawberry is built so a human reviews before any external action. Skipping that review to save time is how you ship a wrong fact to a real person.

Honest tradeoff vs alternatives

You could research a campaign or partnership before it ships inside Apollo alone using its native features, or with a dedicated campaign research tool. Apollo alone gives you tighter data fidelity but misses every signal that lives off-platform. A specialised campaign research tool gives you better dashboards but its scope ends where its integrations end, and most of the real signal still lives on the open web.

Strawberry can search Apollo by ICP filter, enrich a candidate list with verified emails, and combine that with web research for personalized outreach. That's where the Strawberry + Apollo combination earns its keep. The price you pay: an agent run takes 30-90 seconds; a native Apollo action loads in 2. For a one-off question you already know the answer to, use Apollo directly. For an output you'll redo every week or every account, route it through Strawberry as a saved routine so the synthesis happens once and re-runs automatically.

What a real output looks like

• Campaign: AI browser launch on Meta Ads - Nordic ICP
• Audience: founders + ops leads at 10-200 person SaaS companies in SE/DK/NO
• Channels: Meta Ads (primary), LinkedIn (secondary), founder LinkedIn organic
• Messaging: 'The browser that does the boring work' - 3 variants
• Risks: Meta still needs Business Verification stable; budget capped at €500/wk in test phase