Questions about EndFrame, answered.

EndFrame (endframe.io) is a first-party conversion tracking platform with server-side conversion pixels built in. It collects visits and actions through one snippet, turns them into conversion goals, credits each conversion to the campaign and source of the visit that converted, and forwards it server-side to Meta, GA4, TikTok, or a webhook with event-ID deduplication, so a conversion your browser pixel missed on iOS or behind an ad blocker can still be counted, as long as EndFrame's own snippet recorded it.

EndFrame is built for performance marketers, growth teams, and agencies running real ad spend on Meta and TikTok, and measuring in GA4, who are losing conversions to iOS, Safari, cookie restrictions, and ad blockers. It fits teams that want server-side conversions and campaign-level conversion reporting without hosting a server-side GTM container or stitching several tools together.

Start a free trial, connect the domain you want to measure, create a campaign and install its snippet, map your UTM parameters, define a conversion goal, and toggle on a server-side destination such as Meta Conversions API. The setup is designed so you can forward a first conversion in about twenty minutes.

No. You can start free for 14 days with 3 seats and 20,000 tracked visits, no credit card required. The REST API and MCP server start on paid plans.

Usually not. Installing the tracking snippet is similar to adding a standard analytics tag, parameter mapping and conversion goals are configured in the dashboard, and server-side destinations are toggles that take platform credentials. There is no server-side GTM container to host, so most teams get started without an engineering project.

The dashboard brings together the work teams do every day: define conversion goals, toggle server-side destinations for Meta, GA4, TikTok, and webhooks, review reporting and an optional live view, check engagement time and scroll depth KPIs, create and maintain campaigns with the inline editor, manage connected domains, keep source mapping clean, manage API keys, and control team access through roles and policies.

Reporting gives you visibility into visit and action volume over time, along with average engagement time, average scroll depth, top campaigns, and top sources. Language and screen resolution breakdowns are available in the analytics explorer, and everything can be exported to CSV.

You create a campaign using the inline editor with live embed snippet preview and a copy button. Parameter mapping is built into campaign setup, inline validation catches errors before launch, and you can duplicate any campaign to create variants without rebuilding from scratch.

The tracking snippet automatically captures visits, actions, scroll depth, engagement time (active seconds via the Visibility API), screen resolution, viewport size, browser language, and connection type. No extra configuration is needed.

Yes, as conversions. The snippet records form submissions automatically, and you can send your own events with endframe.track. Define a lead conversion goal on a form-submit event or a thank-you page URL, and EndFrame credits each lead to its campaign and source and forwards it server-side to Meta, GA4, TikTok, or a webhook into your CRM. EndFrame does not store contact details in a lead inbox; your form tool or CRM stays the system of record.

EndFrame focuses on conversion tracking and campaign attribution, and it runs alongside your existing tools rather than replacing them: it forwards conversions to GA4 and to your ad platforms, and you can keep browser pixels in place. Teams typically use it as the source of truth for campaign conversions while keeping product analytics elsewhere.

A lightweight tracking snippet on your site sends events to EndFrame, which records visits as sessions and the actions taken within them. That gives you both traffic volume and the meaningful actions behind it.

Parameter mapping defines how incoming query parameters are captured and normalized into clean, report-ready dimensions. It is what turns inconsistent raw inputs into source data you can actually trust in reporting.

Mapping rules normalize incoming parameters as traffic arrives, so variations like differing casing or naming collapse into a single consistent source. Validation surfaces unmapped or unusual values early, before they spread across weeks of reports.

Yes. You can connect multiple domains and run campaigns across them, with per-domain reporting on coverage and activity, which is helpful for teams and agencies managing several brands. Access control applies to the whole workspace; roles cannot be limited to individual domains.

After installing the snippet, use the reporting overview and campaign activity views to confirm visits and actions are arriving, and check the validation signals on the dashboard's UTM & Parameters page to make sure source identifiers look correct.

Meta Conversions API (Facebook and Instagram ads), GA4 Measurement Protocol, TikTok Events API, and custom webhooks for a CRM, warehouse, or any HTTPS endpoint. Each destination is a toggle in the dashboard that takes the platform's credentials, and you can enable several destinations for the same conversion goal.

No. Traditional server-side tagging needs a server-side GTM container with its own hosting, templates, and maintenance. EndFrame already owns the first-party event stream, so forwarding a conversion is a destination toggle rather than a tagging project. You can keep server-side GTM for other jobs if you already run it.

Every server-side event carries an event ID. If your site passes the same event_id it gives the browser pixel, EndFrame reuses it; otherwise it derives a stable ID from the recorded action. Meta and TikTok collapse a browser event and a server event that share an ID and event name, so you recover lost conversions without double counting.

Partly. When an ad blocker or Safari ITP stops or limits the Meta, GA4, or TikTok browser pixel, EndFrame can still forward the conversion server-side, as long as EndFrame's own snippet recorded it. The snippet currently loads from and sends events to EndFrame's domain rather than a subdomain of your site, so an ad blocker that lists that domain blocks EndFrame's collection too. The recovery calculator's percentages are industry benchmarks, not measured EndFrame results.

Keep it. The recommended setup is redundant: the browser pixel fires where it can, EndFrame forwards the same conversion server-side with a shared event ID, and the platform keeps one copy. Removing the pixel is possible but forfeits the browser signals that improve match quality.

Identifiers such as email and phone are normalized and SHA-256 hashed per platform before they leave EndFrame. Browser-scoped values like Meta's fbp and fbc are passed as-is, as Meta requires. GA4 receives the visitor's client ID rather than hashed personal data. You control which identifiers your snippet collects.

Not today. EndFrame forwards to Meta, GA4, TikTok, and webhooks. Google Ads Enhanced Conversions, offline conversion import, and the Pinterest, Snapchat, and LinkedIn conversion APIs are not supported. A webhook can carry conversions to a system of your own that feeds those platforms.

Yes, on any site where you can add a script tag. EndFrame installs as a JavaScript snippet rather than a platform app, so it works on Shopify, WooCommerce, WordPress, Webflow, Wix, Squarespace, and custom builds. There is no native app store listing and no order webhook sync: purchases are recorded by the snippet through a thank-you page goal or an endframe.track purchase event. Shopify only lets tracking code run on its checkout and thank-you pages through Customer Events (a custom pixel), so contact us for custom pixel snippet guidance there. The platform tracking-audit guides cover the specifics of each stack.

Deliveries are queued with automatic retries and exponential backoff, and every attempt is logged with its status per destination. A rejected event, an expired access token, or a platform outage shows up in the delivery log instead of silently dropping conversions. To verify before going live, use Send test: it always goes to each platform's test path, so a test never reaches live data (Meta and TikTok need a Test Event Code first). A destination's Test mode sends all of its events to that test path.

EndFrame records the visit, the actions inside it, and the conversion as one auditable chain, and credits the conversion to the campaign and source of the visit that converted. Reporting breaks conversions down per campaign and per source. This is campaign-level conversion credit from a single first-party chain you can inspect, not a modeled multi-touch or cross-channel attribution algorithm.

EndFrame collects first-party data through your own snippet, hashes personal identifiers before forwarding, and isolates each workspace's data. It does not include a consent management platform, so you keep your existing consent banner and decide when the snippet loads. Ask through the contact page for details on data handling for your region.

Server-side destinations for Meta Conversions API, GA4 Measurement Protocol, TikTok Events API, and custom webhooks on every plan, plus a read-only REST API and a read-only MCP server for AI agents on paid plans. There are no paid add-ons.

The MCP server implements the Model Context Protocol using JSON-RPC 2.0 and exposes 8 read-only tools that let AI agents query your campaigns, domains, goals, conversions, visits, and analytics. It uses the same API keys as the REST API and is available on paid plans.

On a paid plan, create a named API key on the Developers page of the dashboard and start making HTTP GET requests. The API is read-only, returns JSON, and covers analytics, campaigns, domains, goals, and conversions.

API keys are created and managed on the Developers page of the dashboard, and the REST API and MCP server accept them on paid plans. You can name each key, enable or disable it without deleting, and revoke it permanently. Keys are workspace-scoped, so they only access data within your workspace.

Yes. The dashboard supports CSV export for analytics data including engagement time, scroll depth, language, and screen resolution breakdowns. The REST API provides programmatic access for ongoing integrations with BI tools and external dashboards.

EndFrame offers Starter and Growth self-serve plans plus a custom Enterprise plan for larger organizations. You can compare current pricing and capabilities on the pricing page.

Yes. Start free for 14 days with 3 seats and 20,000 tracked visits. Use it to set up domains, campaigns, goals, and server-side destinations before committing, with no credit card required. The REST API and MCP server start on paid plans.

Plans are sized around the things that scale with usage: connected domains, campaigns, tracked visits per month, seats, and API calls per month. Higher plans raise these limits. Every plan includes the same server-side destinations. Billing is monthly.

Yes. Plans are designed to grow with you, so you can move to a larger plan as your campaign volume and team expand, or adjust as your needs change.

Yes. The Enterprise plan is for larger organizations that need custom limits, dedicated support, and hands-on rollout guidance. Reach out through the contact page to discuss requirements.

EndFrame uses role-based access control. Workspace owners have full access. Each teammate gets a role defined by EndFrame that sets read, write, and delete access per area of the workspace; the built-in User role is read-only. Roles are the same on every plan, and you can't create your own roles yet.

Yes. Navigation is policy-aware, so people only see the resources they are allowed to access, while workspace owners keep full control.

Each customer operates in their own workspace, and campaigns, domains, goals, destinations, reporting, API keys, and team membership are all scoped to that workspace.

Workspace owners add and remove users and choose each user's role. A teammate can add users and change roles only if their role includes write access to Users, and can remove users only if it also includes delete access to Users; the built-in User role is read-only and can't manage the team. The roles themselves, and the permissions inside them, are defined by EndFrame.

Support scales with your plan, from email support on Starter to priority support on Growth and dedicated support on Enterprise. You can also reach the team any time through the contact page.

Yes. If you want to discuss your use case, traffic volume, or rollout before starting, contact the team through the contact page and we will follow up.

Reporting and read access remain available, while changes that modify your workspace are paused if a subscription becomes past due or is canceled, so your data stays intact while billing is resolved.