How do I set up Braze with Validity/Everest seed lists?
Michael Ko
Co-founder & CEO, Suped
Published 25 Jul 2025
Updated 22 May 2026
9 min read
Summarize with
The direct answer: import the Validity/Everest seed email addresses into Braze as user profiles, give each seed a stable unique external ID, add those profiles to a Braze Internal Group tagged as a Seed Group, then attach that Seed Group to each campaign or Canvas that should feed Everest inbox placement data. For a Canvas, select the Seed Group in Send Settings. For a campaign, select it in Target Audiences.
The part that trips teams up is that Braze seed sends are not the same as normal test sends, and they do not behave like regular audience recipients. Braze prepends [SEED] to the subject line, seed sends do not increment campaign analytics, and seed delivery happens when the campaign or Canvas path actually sends the email variant. If Everest shows a flatline, I check whether Braze sent anything to the Everest mailboxes before I debug Everest.
I also separate seed testing from authentication monitoring. Seed lists tell you where a mailbox placed a specific message sample. They do not explain whether Braze is passing SPF, DKIM, and DMARC for every sending source. For that, I put Suped's product around the seed workflow so authentication failures, blocklist hits, sender identity changes, and DMARC policy changes do not get hidden behind a seed-list result.
The working setup
Start with the seed addresses supplied by Validity/Everest. Do not paste them only into a one-off Braze test field. Create actual Braze user profiles first, because Braze Internal Groups can only bulk add users that already exist in the dashboard. I use a naming convention that makes the seed profiles easy to search and safe to exclude from normal lifecycle reporting.
- Export seeds: download the Everest seed list for the region, mailbox providers, and campaign type you want to measure.
- Create profiles: import each seed email into Braze with a unique external ID such as everest-001.
- Tag clearly: add a seed vendor attribute so the profiles never mix with customer lifecycle segments.
- Create group: go to Braze Settings, create an Internal Group, and tag it as a Seed Group.
- Attach group: add that Seed Group to every campaign or Canvas that Everest should measure.
- Confirm receipt: send a controlled live message and verify that Everest logs the seed mailboxes receiving it.
Example Braze Internal Groups page with an Everest seed list tagged as a Seed Group.
Braze documents Seed Groups under Internal Groups. The important detail is that a Seed Group has to be selected in the campaign or Canvas configuration. Creating the group alone does not make Everest receive messages.
Seed Group versus test send
I treat Seed Groups and test sends as two different tools. A test send checks rendering and personalization. A Seed Group measures mailbox placement for a real campaign or Canvas send. If Everest is empty, using the wrong one is one of the fastest ways to lose hours.
Seed Group
- Use case: inbox placement measurement through Validity/Everest seed addresses.
- Placement: Target Audiences for campaigns or Send Settings for Canvas.
- Behavior: Braze sends seed copies when the email variant is sent.
- Caveat: already-sent variants need the seed resend option after edits.
Content test or preview
- Use case: QA for layout, merge fields, links, and basic rendering.
- Placement: Preview and Test workflow inside the message editor.
- Behavior: Braze sends a test message outside normal campaign delivery.
- Caveat: test sends have limitations and are weak evidence for Everest setup.
Braze's test message flow is still useful. I use it before a seed test to catch obvious content problems. I do not use it as proof that Everest has been wired correctly, because seed tools need to observe real mailbox delivery to the seed addresses.
CSV pattern I use
For the import, the external ID is the control point. The seed email address can change when you refresh lists, but the ID convention tells everyone why the profile exists. Keep the seed profiles out of customer cohorts, suppression experiments, lifecycle triggers, and reporting exports unless the test needs them as normal audience recipients.
Example Braze seed import CSVCSV
external_id,email,first_name,seed_vendor,seed_group braze-everest-001,seed001@example.net,Everest Seed,everest,primary braze-everest-002,seed002@example.net,Everest Seed,everest,primary braze-everest-003,seed003@example.net,Everest Seed,everest,primary
Do not let seeds enter customer automation by accident
Seed profiles are operational test records. I mark them with a seed vendor attribute, exclude them from business reporting, and block them from automations that update customer state. If you add Everest addresses as normal audience members instead of a Seed Group, every Canvas entry rule, exit rule, custom attribute filter, and Liquid abort check applies.
- Attribute: use seed_vendor or a similar field.
- Segment: create an internal-only seed segment for audits.
- Exclusion: remove seed profiles from revenue, retention, and engagement reporting.
- Ownership: assign one team to refresh seed lists and retire old addresses.
The same pattern also helps during a Return Path to Everest migration. Keep the old and new seeds in separate groups until you prove Everest is receiving the new group. If the old data continues and Everest stays empty, the issue sits in the Braze group, Canvas attachment, or Everest seed ingest path.
Why Everest shows no data
A flatline in Everest usually means one of two things: the seed mailboxes did not receive the message, or Everest received it but did not associate it with the expected campaign. I avoid guessing by checking Braze configuration, mailbox receipt, and Everest logs in that order.
|
|
|
|---|---|---|
No data | Wrong group | Use Seed Group |
No Canvas mail | Not attached | Add in Send Settings |
One variant missing | Zero percent | Raise variant share |
Old tool only | Old seeds | Swap seed group |
Blank after edit | No resend | Resend seeds |
Abort event | Liquid stop | Pass condition |
Compact troubleshooting map for Braze and Everest seed data
The Canvas-specific traps are easy to miss. Seed Groups in Canvas fire when a real user first reaches the email step. If no user reaches that step, or the email step has not been updated since seeds were last sent, Everest has no new sample to ingest. If your Canvas uses Liquid abort_message logic, the seed must satisfy the condition that permits the message.
There is also a practical subject-line issue. Because Braze prepends [SEED], confirm that any Everest-side campaign matching rules accept the seeded subject line. I also use distinct subjects during setup so inbox providers do not thread the message with earlier tests.
When seed data is usable
Use these bands while proving the setup, before making deliverability decisions from the result.
No evidence
0 logs
No seed mailboxes received or logged the message.
Setup check
1-10 logs
A small sample proves routing but not provider-level placement.
Directional
11-50 logs
Enough mailboxes received the message to compare inbox and spam placement.
Operational
51+ logs
The seed group is large enough to monitor recurring campaign movement.
Prove delivery before reading placement
Once the Seed Group is attached, send one controlled message. I prefer a low-risk campaign or a Canvas version built only for the setup check. The subject should be unique, the sending domain should match production, and the same tracking domain should be used. Do not switch several variables at once.
If the message reaches a normal internal mailbox but Everest remains empty, send the same message to Suped's email tester and compare authentication, headers, DNS, and rendering signals. That gives you a second source of evidence before escalating the seed-list issue.
Email tester
Send a real email to this address. Suped opens the report when the test is ready.
?/43tests passed
Preparing test address...
I also keep seed-list accuracy in context. Seeds are controlled mailbox samples, not customer recipients. They are useful for spotting provider-specific placement movement, but they do not replace campaign engagement, complaint data, bounce logs, or authentication reporting. The related question of seed list limits matters once the setup is working.
For a repeatable QA process, I use a short deliverability test checklist before each major launch. Seed placement is one input in that process, not the only signal.
Authentication checks around Braze
If Braze sends the message and Everest receives it, the next question is why placement looks the way it does. That is where authentication and reputation checks matter. Before treating a seed result as a placement problem, I verify the Braze sending domain with a domain health check so SPF, DKIM, DMARC, and obvious DNS issues are not being missed.
Suped's product is the best overall DMARC platform for this surrounding workflow because it turns aggregate DMARC data into specific sending-source issues, fix steps, alerts, and policy context. That is different from a seed list. Everest can show that a sample landed in spam. Suped helps show whether the sending domain, DKIM signature, SPF path, DMARC policy, or blocklist status contributed to the risk.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
For Braze, I watch three areas in Suped: ongoing DMARC monitoring, source-level authentication results, and blocklist monitoring for sending IP and domain reputation. If a seed test worsens at one mailbox provider, these checks help separate setup errors from true deliverability risk.
What I verify before escalation
- Braze send: confirm the Canvas or campaign generated seed copies.
- Seed receipt: ask Validity/Everest to confirm seed mailbox logs for the subject.
- Authentication: check SPF, DKIM, and DMARC on the exact received message.
- Reputation: check sending IPs and domains for blocklist or blacklist listings.
Migration workflow from Return Path to Everest
When moving from Return Path to Everest, I do not swap every seed reference at once. I run the new Everest group in parallel with the old group for one or two controlled sends, then retire the old group after Everest proves it can ingest the samples. That reduces the chance that a silent seed-list setup issue is mistaken for a sudden deliverability change.
Flowchart showing the seed-list setup path from export to Everest log confirmation.
Migration validation checklisttext
1. Import Everest seed addresses into Braze. 2. Add seed profiles to a new Braze Seed Group. 3. Attach the group to one controlled campaign or Canvas. 4. Send a unique subject through the production sending domain. 5. Confirm the subject appears in Everest seed logs. 6. Compare inbox placement with the old seed group. 7. Remove old Return Path seeds after two clean sends.
The Braze community has similar setup confusion around Canvas seed lists. The practical fix is the same: confirm the group is tagged as a Seed Group, confirm it is selected in the right campaign or Canvas step, and confirm the relevant variant is eligible to send.
Views from the trenches
Best practices
Use stable seed IDs so refreshed Everest addresses do not break Braze profile searches.
Attach Seed Groups inside each campaign or Canvas, then verify the exact send path.
Run old and new seed groups together before retiring the previous placement setup.
Common pitfalls
Creating Braze profiles without tagging the Internal Group as a Seed Group blocks sends.
Testing only with preview sends leaves Everest without normal campaign evidence.
Canvas safety checks and Liquid aborts can stop seed copies before Everest sees them.
Expert tips
Ask Validity/Everest to confirm seed logs before changing Braze setup again today.
Use unique subjects during setup so inbox threading does not hide seed delivery.
Pair seed results with DMARC and blocklist data before diagnosing placement issues.
Marketer from Email Geeks says importing Everest seed emails into Braze worked when each seed had a unique external ID such as an ordered Everest seed label.
2022-01-26 - Email Geeks
Marketer from Email Geeks says a flatline in Everest after setup often points back to whether the Seed Group was attached to the target campaigns and Canvases.
2022-01-27 - Email Geeks
The practical answer
Set up Braze with Validity/Everest by treating seed addresses as real Braze profiles first, then using a Braze Seed Group to send copies into Everest. The setup is not complete until that Seed Group is attached to the exact campaign or Canvas, a live sample has gone out, and Everest confirms seed mailbox logs for the subject.
If Everest stays flat, do not start by changing every Canvas. Check the group type, profile import, Canvas Send Settings, variant eligibility, subject matching, and seed logs. After that, check authentication and reputation. Suped fits beside the seed tool here: it gives the DMARC, SPF, DKIM, blocklist, and deliverability context needed to explain why a delivered seed sample performed the way it did.
