| Is the newsletter list the same reader as the paywall?Favours EdgeKit | Your lists and subscriber data stay in your ESP. Embrin syncs with Braze and others for subscription rules, audience segments and engagement signals. | Yes. The list sits on the same reader record as sign-in, the paywall and the subscription, and is pushed to your ESP. EdgeKit owns the unsubscribe link and the one-click header, and an unsubscribe made inside your ESP comes back, so the list and the preference never disagree. |
|---|
| Who runs the sign-up and preference pages?Favours EdgeKit | Not Embrin. It holds no newsletter list data; your lists and subscriber data stay in your ESP, so sign-up and preference pages stay wherever you run them today. | EdgeKit holds your subscribers, and your team builds the pages with its SDK: sign-up pages, sign-up flows the decision engine tailors to each reader, and preference pages showing each reader their own lists. |
|---|
| Does the newsletter go out when nobody is at a desk?Favours EdgeKit | Recurring newsletters on a schedule. Embrin picks an edition up when your editors mark it ready in Arc XP, and its pages describe choosing who receives each edition and scheduling the send. | Yes, if you want it to. Set days, times and a timezone and autopilot creates and schedules every edition, and its feeds fill at the moment it sends, so a 7am edition carries what was published at 6:55. |
|---|
| Can the same edition go out as a push notification?Favours EdgeKit | Email, plus a hosted web page for every edition. Those are the channels Embrin’s pages describe. | Yes. An edition carries an iOS and Android push beside the email, filled from a story and editable, sent to its own segment and checked against each platform’s payload limit. |
|---|
| Does it build the edition from Arc XP, or do editors paste it in?Favours EdgeKit | From Arc XP: Composer content, WebSked schedules, edition structures and content locks. Editors keep working in Arc XP, and Arc XP is its deepest integration today. | From Arc XP and any other CMS vendor, synced continuously: stories pitched from WebSked, feeds by section, tag, content type or author, and editors’ own picks and text. A story scheduled in your CMS but not live by the send is left out. |
|---|
| What stops a broken edition going out?Neither | Checks before every send for broken links, missing images, draft content, payload size, Gmail clipping and rendering issues. | Checks that hold the send until they pass: a subject on every version, an email that renders, the sending setup in place and push within its limits. A story not live by the send is flagged and left out, and Gmail clipping is flagged before you send. |
|---|
| Do we have to change our email platform?Favours EdgeKit | No. Braze is included from the Basic tier, Mailchimp and Resend are listed as compatible, and Embrin says it will integrate whichever ESP you already use, for a fee. | No, if it is Braze, SendGrid or Resend: EdgeKit renders the edition and your platform delivers it. Any other platform is added at no charge. |
|---|
| Can we sell sponsorship inside the newsletter?Favours Embrin | Yes. Native ad slots for house ads and direct-sold sponsors, which your team places, previews and traffics in Embrin. | Through the email ad manager you choose, such as LiveIntent, Passendo or Kevel, with its placements built into your template. EdgeKit’s own ad manager is in development. |
|---|
| Is every edition on the web?Neither | Yes, automatically: every edition is a hosted web page, shareable and indexable by search engines. | When you switch it on: a public archive per publication on your own domain, one shareable page per edition, indexed by search engines only if you choose and hideable edition by edition. |
|---|