From f814e8a8aacc314eb2b23fa551c4f059a56437b9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yusuf=20To=CC=88r?= <3296904+yusuftor@users.noreply.github.com> Date: Tue, 25 Aug 2026 21:00:50 +0200 Subject: [PATCH 1/3] docs(integrations): move Meta Ads allow-list domain to install.link Superwall's MMP ad links now live on install.link instead of mmp.superwall.com, and the event_source_url on conversion events sent to Meta's Conversions API carries the install.link domain. Update the traffic-permissions step and the troubleshooting bullet to instruct allow-listing install.link, noting that an existing superwall.com entry can stay for links created before the move. Documents superwall/paywall-next#3927. Co-Authored-By: Claude Fable 5 --- content/docs/integrations/meta-ads.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/integrations/meta-ads.mdx b/content/docs/integrations/meta-ads.mdx index 7f793584..f4476341 100644 --- a/content/docs/integrations/meta-ads.mdx +++ b/content/docs/integrations/meta-ads.mdx @@ -91,8 +91,8 @@ Meta requires you to acknowledge new custom events and allow the domain they com ![A confirmed sw_subscription_start event listed in the dataset's Overview events table under the Conversions API integration](/images/mmp_meta_events_confirmed.jpg) - - In your dataset's **Settings**, under **Traffic permissions - websites**, click **Create allow list** and add `superwall.com`. + + In your dataset's **Settings**, under **Traffic permissions - websites**, click **Create allow list** and add `install.link`. That's the domain your ad links live on and the domain Superwall reports as the source of its events. If `superwall.com` is already on the list from an earlier setup, leave it there; it still covers ad links created before Superwall moved to `install.link`. @@ -235,7 +235,7 @@ The **Dataset** dropdown only shows web datasets. If the only dataset you see in - Sandbox purchases are never forwarded. Only production events are sent to Meta; use **Send test events to Meta** to validate before going live. - Confirm the dataset ID and access token still validate by editing and re-saving the configuration. - Confirm the `sw_` custom events in **Review events** in Events Manager. -- Add `superwall.com` to the dataset's website traffic allow list. +- Add `install.link` to the dataset's website traffic allow list. ### No transaction or purchase events From 40ad716943907c2e03272cf4b6ae70aa4359ac51 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yusuf=20To=CC=88r?= <3296904+yusuftor@users.noreply.github.com> Date: Tue, 25 Aug 2026 21:39:49 +0200 Subject: [PATCH 2/3] docs(integrations): drop the superwall.com transition note No real customers added superwall.com to their allow list yet (only internal testing), so the note about keeping it listed is unnecessary. Co-Authored-By: Claude Fable 5 --- content/docs/integrations/meta-ads.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/integrations/meta-ads.mdx b/content/docs/integrations/meta-ads.mdx index f4476341..f54f51a0 100644 --- a/content/docs/integrations/meta-ads.mdx +++ b/content/docs/integrations/meta-ads.mdx @@ -92,7 +92,7 @@ Meta requires you to acknowledge new custom events and allow the domain they com ![A confirmed sw_subscription_start event listed in the dataset's Overview events table under the Conversions API integration](/images/mmp_meta_events_confirmed.jpg) - In your dataset's **Settings**, under **Traffic permissions - websites**, click **Create allow list** and add `install.link`. That's the domain your ad links live on and the domain Superwall reports as the source of its events. If `superwall.com` is already on the list from an earlier setup, leave it there; it still covers ad links created before Superwall moved to `install.link`. + In your dataset's **Settings**, under **Traffic permissions - websites**, click **Create allow list** and add `install.link`. That's the domain your ad links live on and the domain Superwall reports as the source of its events. From 2d5c0c4881a8b08c8795fe60d742b46f35fcc140 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yusuf=20To=CC=88r?= <3296904+yusuftor@users.noreply.github.com> Date: Tue, 25 Aug 2026 21:57:12 +0200 Subject: [PATCH 3/3] docs(integrations): trim the allow-list step to the bare instruction Co-Authored-By: Claude Fable 5 --- content/docs/integrations/meta-ads.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/integrations/meta-ads.mdx b/content/docs/integrations/meta-ads.mdx index f54f51a0..edfb96ea 100644 --- a/content/docs/integrations/meta-ads.mdx +++ b/content/docs/integrations/meta-ads.mdx @@ -92,7 +92,7 @@ Meta requires you to acknowledge new custom events and allow the domain they com ![A confirmed sw_subscription_start event listed in the dataset's Overview events table under the Conversions API integration](/images/mmp_meta_events_confirmed.jpg) - In your dataset's **Settings**, under **Traffic permissions - websites**, click **Create allow list** and add `install.link`. That's the domain your ad links live on and the domain Superwall reports as the source of its events. + In your dataset's **Settings**, under **Traffic permissions - websites**, click **Create allow list** and add `install.link`.