Reply.io
Cold email and sales outreach. A Piksio image goes into Reply.io 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”Reply.io writes merge tags like {{FirstName}}.
Reply.io 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 Reply.io’s own fields automatically:
| Piksio field | Reply.io field |
|---|---|
first_name |
FirstName |
company_name |
Company |
Custom fields
Section titled “Custom fields”Any other field must exist in Reply.io before you send. Create a contact custom field. Spaces and special characters in its name become underscores in the variable.
Reply.io’s guide to custom fields
Where to paste
Section titled “Where to paste”Open the template’s HTML view and paste the HTML.
Formats offered: Image URL, HTML. The default for Reply.io 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={{FirstName}}&company_name={{Company}}" width="600" alt="Your personalized image" style="display:block;max-width:100%;height:auto;border:0" />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 Reply.io 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 Reply.io’s own documentation on 2026-10-07: