Datapipe

Social marketing · USE CASE

Find the content worth turning into something more.

Use Facebook Pages engagement, tagged GA4 visits and current WordPress content to choose what to refresh, expand or repurpose.

Facebook PagesGoogle AnalyticsWordPress
Try it with your data Free with up to 3 data sources · No credit card
A WORKED EXAMPLE

Which Facebook posts deserve a stronger website follow-up?

TopicCurrent reactionsTagged GA4 sessions
Setup checklist140220
Product announcement31044

Posts created Oct 5–Nov 1 · Current counters · GA4 period visits

Start with the setup checklist. It has more tagged website visits even though the announcement has more reactions.

EXAMPLE WORKFLOW

Ask. Follow up.
Take the next step.

✦ AI assistantSample workflow
Facebook PagesGoogle AnalyticsWordPress
YOU

  1. 01
    Confirmed post UTM → /guides/setup-checklistFollow up first

    Next

  2. 02
    Confirmed post UTM → /productInspect the mismatch

    Next

Posts created Oct 5–Nov 1 · Current counters · GA4 period visits1 / 3

01 · CONNECT YOUR DATA

Your tools. One place to ask.

3 of 3 Free data sources
No credit card · Daily refresh

DatapipeYour project
Your AI assistantor a report in Sheets / Data Studio
  1. Create your free workspace

    Sign up with your company email. Your first project opens on Data sources.

  2. Add the data sources

    Choose the accounts for this workflow. Authorize access and select the property or site.

  3. Bring your question

    Connect your project to a supported AI assistant, or build your source reports.

Create a free account →
Setup steps & what you need

Email/password signups confirm their email first. Use Google signup with a company account if you prefer.

Start with existing Search Console and GA4 properties collecting data for the same site. Need to install tracking? See Google’s WordPress setup guide.

  • Facebook Pages: Authorize Facebook Pages and select the intended managed Page. Required reporting permissions and account access apply. Setup guide ↗
  • Google Analytics: Authorize Google Analytics and select the GA4 property for the same website. Setup guide ↗
  • WordPress: Enter your site URL, WordPress username, and a dedicated Application Password. Setup guide ↗

Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.

02 · ASK A USEFUL QUESTION

Start with a prompt.
Follow the evidence.

Copy these in order into your connected assistant.
Each builds on the answer before it.

01

Find posts with useful engagement

Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.

Read Facebook Pages posts created in our chosen window with post ID, text, permalink and current reactions/comments/shares. Retain the read timestamp. Do not describe cumulative counters as interactions occurring only in the date range, or assume the counters are organic-only.
02

Follow up across your data sources

Read the full prompt
Use only this Datapipe project’s authorized data sources. Discover the connected accounts, datasets, and fields first. If the right account or required data is missing, ask me rather than substituting sample data. Show the actual dates, filters, coverage, and any partial results.

Read the setup article in WordPress. Draft the stronger website follow-up. Read the actual current records behind the shortlist. Show which source supports each observation, distinguish causes from hypotheses, and propose one specific next step.
03

Put the change into practice

Read the full prompt
Create a WordPress draft for the setup checklist. Use real returned records and verified current values, not the example identifiers or wording. Show the exact proposed change. Prepare the supported action for review in Datapipe; after approval there, apply only the approved change and re-read the source record to verify it. If configured write access or a field is missing, explain what is needed instead of claiming success.

03 · USE WHAT YOU FIND

Inspect the WordPress destination.

  1. 01

    Read current engagement for published Page posts.

  2. 02

    Confirm each post-to-page mapping.

  3. 03

    Inspect the WordPress destination.

Check the result at your next review.

Tag future posts consistently and review their website visits alongside current Page counters. Record the follow-up content and compare compatible periods at the next review.

Implementation tips for this use case

Read the destination’s current title/content and modified date. Compare its promise with the post. Choose a content follow-up after reviewing topic purpose, tracking and website engagement.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to choose social content to repurpose using website context
  1. Read current engagement for published Page posts.

    Read Facebook Pages posts created in the chosen window, retaining post ID, text, permalink and current reactions/comments/shares. These counters are cumulative and may include paid distribution.

  2. Confirm each post-to-page mapping.

    Use a known UTM content/campaign mapping or a documented manual URL mapping. Read compatible GA4 sessions and engaged sessions. A Facebook permalink alone does not identify the outgoing website link.

  3. Inspect the WordPress destination.

    Read the destination’s current title/content and modified date. Compare its promise with the post. Choose a content follow-up after reviewing topic purpose, tracking and website engagement.

See the complete example report
EXAMPLE REPORTFictional sample data

Which Facebook posts deserve a stronger website follow-up?

Posts created Oct 5–Nov 1 · Current counters · GA4 period visits

Which Facebook posts deserve a stronger website follow-up? · fictional sample data
TopicCurrent reactionsTagged GA4 sessions
Setup checklist140220
Product announcement31044
WHAT TO LOOK ATStart with the setup checklist. It has more tagged website visits even though the announcement has more reactions.

Inspect the WordPress destination.

Illustrative report output · no live query or source change

The Facebook post currently has 140 reactions and 18 shares. Its confirmed UTM mapping shows 220 GA4 sessions, 160 engaged. WordPress provides the current guide to review. The post has 310 current reactions, while the matched GA4 view contains 44 sessions, 18 engaged. High reactions alone do not establish strong website intent.

Try the example with sample CSVs

Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.

Data method, reporting checks & sources

Read Facebook Pages posts created in the chosen window, retaining post ID, text, permalink and current reactions/comments/shares. These counters are cumulative and may include paid distribution. Use a known UTM content/campaign mapping or a documented manual URL mapping. Read compatible GA4 sessions and engaged sessions. A Facebook permalink alone does not identify the outgoing website link. Read the destination’s current title/content and modified date. Compare its promise with the post. Choose a content follow-up after reviewing topic purpose, tracking and website engagement.

The outgoing website URL is established through a verified mapping. Current/lifetime post counters are separated from GA4 period data. Paid distribution is not assumed to be organic engagement.

  • The outgoing website URL is established through a verified mapping.
  • Current/lifetime post counters are separated from GA4 period data.
  • Paid distribution is not assumed to be organic engagement.
  • Access to the intended Facebook Pages account or property.
  • Access to the intended Google Analytics account or property.
  • Access to the intended WordPress account or property.
  • The outgoing website URL is established through a verified mapping.

For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions. This is an illustrative workflow; live accounts and destinations need their own setup.

A FEW USEFUL ANSWERS

Before you start.

Can reactions tell me which posts drove sales?

Not by themselves. Reactions and shares describe Page engagement. Website behavior needs a confirmed link/UTM mapping and appropriate analytics evidence.

Are post counters limited to the selected publication dates?

The dates select which published posts are returned. Their reaction/comment/share counters are current cumulative values, rather than activity occurring only during those dates.

YOUR NEXT STEP

Try it with your own data.

Start free with up to 3 data sources. No credit card.

Start free →