Skip to main content

Dynamic Images (Street View)

What it is​

Dynamic images personalize the visual design of each mailer with images unique to that recipient or property. Instead of the same static design going to everyone, each piece can show a photo of the recipient's house, the subject property you're marketing, or product images from their purchase history.

Three options:

  • Google Street View - automatically includes a photo of the recipient's property on the mailer
  • Target Property - for Neighbor Blast and Absentee Owner Mode: shows the target property, not the recipient's property
  • Hyper-Personalization - include recipient-specific images (product photos, specific house, any image URL) via your CRM or API

Enabling Street View on an Image Template​

  1. In the nav bar, go to Image Templates.
  2. Click Dynamic Builder.
  3. Set the Background Image to ~STREET_VIEW~.
  4. Add a header and subheader — for example:
    • Header: "Just Listed on Your Street"
    • Subheader: "See what's happening in your neighborhood."
  5. Save the Image Template.

Subject Property: when to use it​

Use Subject Property when:

  • You're running a Neighbor Blast campaign for a Just Listed / Just Sold property - neighbors see the listing, not their own house
  • You're targeting absentee owners - the mailer shows the investment property you want them to sell

Do NOT use Subject Property on a standard Days After Added campaign unless the target property is intentionally different from the recipient's address.

Showing a different address in Google Street View or Map View​

By default, the Street View or Map View image uses the recipient's own mailing address. If you want the Google image to show a different address (for example, an absentee owner's investment property), map the Absentee Address field in the recipient record to the address you want shown. You can set this field on CSV upload, via Zapier, or through the API.

Hyper-Personalization​

Hyper-Personalization is configured per-send via the API or via CRM integrations. Pass an image URL for each recipient as a custom field and reference it in the Image Template design. See API documentation for field details.

Dynamic Image Template variable reference​

Dynamic image templates use ~VARIABLE~ (tilde) syntax in the header, subheader, QR code, background image, overlay image, and other fields.

Here is an example of how the variables appear in a dynamic card:

Dynamic postcard showing personalized address in header and Street View property image

And the corresponding template settings:

Dynamic Image Template settings showing tilde variables in the header and image fields

Recipient variables​

VariableWhat it inserts
~FULL_NAME~Recipient's full name
~FIRST_NAME~Recipient's first name
~LAST_NAME~Recipient's last name
~COMPANY~Recipient's company name
~ADDRESS~Street address line 1
~ADDRESS2~Address line 2
~CITY~City
~STATE~State
~ZIP~ZIP code
~EMAIL~Recipient's email address
~PHONE~Recipient's phone number
~CUSTOM1~–~CUSTOM10~Custom fields from the recipient record
~ABSENTEE_STREET~The absentee/target property address (Neighbor Blast and Absentee Owner Mode)
~MESSAGE_QR~Uses the same QR code URL set on the paired Message Template

Custom field image URLs in Dynamic Builder​

In Dynamic Builder image URL fields, you can use recipient custom field tokens as image sources.

Supported fields:

  • Background Image
  • Logo Image URL
  • Overlay Graphic

Supported tokens:

  • ~CUSTOM1~ through ~CUSTOM10~

At send time, each token resolves to that recipient's custom field value. If the value is a valid image URL (PNG or JPG), it is rendered in the final generated image.

What this enables:

  • Recipient-specific background images
  • Recipient-specific logos or brand images
  • Recipient-specific overlay graphics
  • Flexible templates that source image assets from recipient data instead of hardcoded URLs

How it works:

  • The Dynamic Builder editor accepts custom field tokens in image URL fields.
  • Preview rendering shows a placeholder image when a custom field token is used as an image source.
  • At send time, the system resolves each recipient's custom field value into the final image URL.
  • If the custom field is missing or not a valid image URL, that recipient is skipped and the order is flagged with an error.

VisitorView variables​

These variables are populated when a recipient is captured via the thanks.io website tracking script. They carry data about the web page the visitor came from.

VariableWhat it inserts
~VV_TITLE~Title of the page that captured the recipient
~VV_IMAGE~Meta/OG image from the page that captured the recipient
~VV_LAST_URL~URL of the page that captured the recipient

Tips & best practices​

  • For real estate, Street View on the recipient's property makes the mailer feel unmistakably personal - recipients recognize their own house immediately.
  • Street View quality varies by address. Rural or newer developments may have lower-resolution imagery. Preview with a sample address before a large campaign.
  • Hyper-Personalization is most powerful combined with CRM triggers (e.g., send a product-image postcard the day after a cart abandonment).
  • VV_ variables are only populated for recipients captured by the VisitorView tracking script. They will be blank for recipients added via CSV or manually.

Limits & gotchas​

  • Street View uses Google Street View imagery - coverage and recency depend on Google's data.
  • Dynamic images add processing time per piece.