---
title: Solutions by use case, stack and team | Plainrouter
description: Find the right Plainrouter workflow for Meta conversion tracking, creative preparation and governed AI agents. Explore setup requirements by stack and team.
canonical: https://plainrouter.com/solutions
last_updated: 2026-09-23
---

# Meta ad workflows for your stack and team.

Choose a workflow for your goal, the stack you run, or the team doing the work. Plainrouter connects first-party conversion signals with governed Meta creative preparation.

[By use case](#by-use-case) · [By stack](#by-stack) · [By team](#by-team)

Stack pages explain custom implementation paths and native alternatives. They are not a catalog of one-click connectors.

## By use case

Start with the job you need to do.

- [Meta Conversions API](/library/meta-conversions-api) — Understand eligible server events, delivery and deduplication.
- [Server-side tracking](/product/signals) — Collect first-party signals and investigate event delivery.
- [Creative testing](/product/launch) — Prepare approved Meta ad copies that stay paused until you activate them.
- [AI agents for ads](/product/actions) — Let agents prepare supported creative work within account and approval boundaries.
- [Approval guardrails](/product/actions#how-it-works) — Follow proposals through policy checks, human approval and verification.
- [Consent-aware measurement](/library/server-side-consent) — Carry real permission decisions into collection and server events.

## By stack

Find the implementation path and the limits of your platform.

- [Shopify](/solutions/shopify) — Compare native Meta sharing with a custom storefront or backend path.
- [WordPress](/solutions/wordpress) — Separate maintained browser code from trusted server event delivery.
- [Webflow](/solutions/webflow) — Keep collection in the site and verified conversions in a separate backend.
- [Next.js](/solutions/nextjs) — Use the browser snippet and Node.js SDK with one purchase owner.
- [n8n & Make](/solutions/automation) — Map eligible website events through HTTP workflows with stable retry identity.
- [Wix](/solutions/wix) — Evaluate native CAPI first, then assess custom-code and consent requirements.
- [Squarespace](/solutions/squarespace) — Plan around checkout restrictions and post-purchase code surfaces.

## By team

Match the workflow to the people doing the work.

- [Developers](/solutions/developers) — Use APIs and MCP for bounded, inspectable advertising tasks.
- [Growth teams](/solutions/growth-teams) — Connect conversion questions to reviewed creative experiments.
- [Agencies](/solutions/agencies) — Keep each client’s context, credentials and review responsibilities clear.

## Start with one concrete workflow

Inspect a conversion event, connect an account-scoped agent, or prepare one creative proposal. Supported creative execution requires human approval; new ad copies are created paused.

[Get started](/register) · [See pricing](/pricing)