Apollo
Cold email and sales outreach. A Piksio image goes into Apollo as an ordinary image link. The platform fills in each recipient’s values, and Piksio renders their version when the email is opened.
Merge tags
Section titled “Merge tags”Apollo writes merge tags like {{first_name}}.
Apollo doesn’t URL-encode values inside links, so keep personalized fields free of & and # (they can cut the link short).
Built-in fields
Section titled “Built-in fields”Piksio maps these to Apollo’s own fields automatically:
| Piksio field | Apollo field |
|---|---|
first_name |
first_name |
last_name |
last_name |
company_name |
company |
Custom fields
Section titled “Custom fields”Any other field must exist in Apollo before you send. Create a contact custom field. Apollo then adds a matching dynamic variable to the { } menu.
Apollo’s guide to custom fields
Where to paste
Section titled “Where to paste”Switch the email step to raw HTML mode and paste the HTML, then preview a contact.
Formats offered: Image URL, HTML. The default for Apollo is HTML.
Example
Section titled “Example”For a design with first_name and company_name, the HTML looks like this:
<img src="https://app.piksio.com/i/YOUR_IMAGE_ID?first_name={{first_name}}&company_name={{company}}" width="600" alt="Your personalized image" style="display:block;max-width:100%;height:auto;border:0" />Good to know
Section titled “Good to know”- Apollo doesn’t send an email when a contact has no value for a variable in it - even one inside the image link. Map only fields every contact has.
Check before you send
Section titled “Check before you send”- In Use in email, use Test the link with sample values, and again with unfilled tags. Both are free.
- Preview one real recipient in Apollo to confirm it fills in the fields.
- See Fallbacks and blanks for what a recipient with missing data sees.
Sources
Section titled “Sources”Checked against Apollo’s own documentation on 2026-10-07: