Read Meta advertising results

Tilgjengelig i alle planerSlik gjør duÅpne i DealJourney

Meta reporting is an internal pilot enabled for the DealJourney ApS workspace. It reads advertising data; it does not publish, pause or edit ads. Other workspaces do not gain access by opening the page.

Connect an account

Open Tilkoblinger in the Marketing sidebar. A DealJourney administrator connects read access and chooses the accounts under Kontoer som skal importeres. Select only the accounts that belong in this workspace, then use Lagre valgte kontoer.

Koble til Meta uses Meta sign-in when the server's app credentials and redirect address are configured and DealJourney is opened through HTTPS. On HTTP localhost, sign-in is unavailable; the adjacent information button explains the secure-address requirement. The internal pilot also has Bruk pilottilgangstoken. This accepts a user access token issued for the DealJourney Meta app with ads_read permission. The server encrypts the token and never returns it to a browser. An expiring token must be replaced; a successful connection is not permanent Meta approval.

If Meta withdraws advertising-read permission, the next failed report checks the grant and asks you to Koble til Meta på nytt. Page lead access is separate and does not replace advertising permission. A server app configuration failure does not disconnect your workspace's otherwise valid grant.

Use Importer nå to import the last 90 days of campaign spend. On hosted environments, enabled accounts refresh hourly and revisit the recent 28 days for revised conversions and spend. Local development does not run that automatic importer.

Import Meta form leads

Open Tilkoblinger, then Leads fra Meta-skjemaer. This is a separate connection from advertising reports. A DealJourney administrator uses Koble sider for leads to grant Page lead access. The pilot token option requires the same Page permissions. Having access to an ad account alone does not grant access to its Page's lead responses.

If an authorized Page is missing, enter its numeric Facebook-side-ID and choose Koble til side. Meta verifies access before the Page is saved; this does not enable imports. Reconnecting verifies previously added Pages directly and preserves their form selections. If access cannot be verified, the reconnect fails without removing the existing configuration.

Use Hent skjemaer on the desired Page. Open Koble felt for a form and select the matching CRM fields. Map at least a name, company or email; each CRM field may be used once. Other answers are preserved in the lead timeline. Use Lagre og aktiver import only for forms belonging in this workspace. Hosted imports check enabled forms every five minutes; locally, leave Connections open during a requested import.

Importer nå reads the available history. Repeated submissions with the same Meta lead ID are skipped, including after disconnecting and reconnecting. Separate submissions from the same person create separate leads; existing people are not merged or overwritten. The lead's source is Meta Lead Ads. Its timeline retains every submitted answer, the originating Page/form/ad identifiers and submission time. Custom disclaimer answers are preserved as evidence, not converted into email/SMS opt-in. Existing lead-created outreach workflows are not dispatched by this importer.

Sett import på pause stops future imports for that form. Disconnecting removes the lead credentials and stops all its forms; it keeps already imported CRM records and duplicate-prevention receipts. A failed page is rolled back together, shows an error, and can be retried after correcting access or mappings. Success means the complete pagination chain finished. Only history still available from Meta can be recovered.

This imports Meta Instant Form submissions. Website registration statistics do not expose contact identities; those leads must arrive through the website's own registration/form integration and tracking.

Explore a report

Open Oversikt or Betalte annonser. Choose the account and dates. Dates use the ad account's timezone and amounts use that account's currency.

Choose Kampanjer, Annonsesett or Annonser. Selecting a campaign drills into its ad sets; selecting an ad set drills into its ads. The breadcrumb returns to the parent. The column selector offers delivery performance, engagement and video metrics.

Detaljer shows the retrieved delivery metrics, events and event values. Fordelinger reports platform, placement, age and gender, country or device separately. Meta may restrict a breakdown or omit a metric; an unavailable value is not shown as zero.

Oppdater requests a fresh report. Large reports prepare in the background with visible progress. The last completed report remains visible while it refreshes, and a failure is shown explicitly. On the overview, this refreshes the table, totals and daily trend together. Expired Meta access produces one connection message, rather than separate failures for each report. Use Koble til Meta på nytt to restore access. A completed historical report remains visible; a failed report without saved results does not continue showing a loading placeholder. Eksporter CSV exports all retrieved rows and metrics for the chosen report, rather than just the visible table page.

Saved reports appear without waiting for a new Meta job. A date range or breakdown that has not been retrieved yet needs Meta to prepare its first report; the progress indicator describes that work. The overview requests separate campaign rows, exact account totals and daily spend, because their metrics cannot all be calculated by adding rows together. Each part appears when available. The last-updated timestamp describes the saved provider data; reopening the page does not itself guarantee a fresh Meta fetch.

Compare individual ads

Choose Annonser in Betalte annonser. Select two to four ads using the checkboxes beside their names, then open Sammenlign annonser. You can select ads across pages of the same report. Changing the account, dates, level or completed report clears the selection.

The Sammenligningsmal offers:

  • Resultater: the selected Konverteringshendelse, its cost, and Meta-reported registrations, leads, purchases, purchase value and ROAS where available.
  • Trafikk: landing-page views, their cost, link clicks, click-through rate and delivery costs.
  • Video: video plays, views at each completion milestone, completion rate and cost per completed play.

Choose a Referanseannonse to see relative costs. Each ad keeps its own spend and result counts visible; the comparison does not add reach or overlapping event types. Missing events remain unavailable rather than becoming zero. A zero reported result count has no calculable cost per result. Results use the ad sets' Meta attribution settings.

Laveste rapporterte kostnad describes the observed cost among selected ads with reported costs. It does not identify a statistically proven winner. Different audiences, budgets, placements and delivery dates can explain differences. This comparison is not a randomized A/B test and does not change ads.

Kvalifiserte leads og kunder explains the remaining attribution gap: qualified CRM leads and confirmed paid customers are not yet linked to individual ads. Meta lead and purchase events must not be interpreted as those confirmed CRM outcomes.

Understand the numbers

Konverteringshendelse selects one Meta event definition. Overlapping action names may describe the same conversion; the report never adds them together. Meta events are separate from confirmed CRM signups, customers and revenue.

CRM-poster — alle kilder shows real workspace-wide CRM records from all sources, including imports and manual entries, created during the selected dates in UTC. These counts do not follow the ad account, campaign or ad filters. Opprettede leadposter counts that cohort of records. Nå kvalifisert eller under bearbeiding counts records currently qualified or nurturing; Nå i salgsfase eller konvertert counts records currently at proposal, negotiation, converted or won. These are current, separate status groups, not successive funnel steps or the dates qualification happened.

Click a count to inspect the underlying leads, recorded sources, statuses and creation dates, then open a lead to review it. At most 500 records are shown; the sheet says when the result may be truncated. Changing dates opens a fresh cohort. Oppdater CRM refreshes CRM counts independently of Meta access. Failed or unavailable counts show a dash rather than zero.

The overview does not label CRM totals or recorded won-deal values as ad-attributed customers, collected revenue or return on ad spend. Those claims require an evidenced link from an ad to a CRM customer and payment.

Reach is requested for the exact report period, rather than added across days or ads. Link click-through rate and cost per link click use link clicks, not all clicks. Media spend can differ from Meta's invoice because of taxes or fees.

Synced spend appears once in Budsjett and is maintained by the connection. Do not import or manually enter the same media spend again. Use Koble markedsføringskampanje beside a Meta campaign to connect its spend to a broader CRM campaign. This does not rename or change the Meta campaign.

Kopier sporingsparametere supplies URL parameters to paste into Meta for future ads. They carry stable campaign, ad-set and ad identifiers through the website and signup into CRM attribution. Existing ads are not changed by copying them, and historical signups cannot be matched without evidence.

Use Koble fra to remove the stored credential and stop imports. Historical analytics and spend remain available to the backend; reconnect and select the account to report on them again.

Disconnecting is separate from a deletion request: it preserves existing CRM leads, timeline answers, reports, synced spend and duplicate-prevention receipts. For removal of Meta-derived data, contact privacy@dealjourneycrm.com with the workspace name and the records concerned. Do not send passwords or access tokens. The request must be verified and scoped with the relevant business before data is removed; sending an email does not mean deletion is already complete.

Var dette nyttig?

Relatert