(888) 278-3433contact@rampedup.io
Data dictionary — October 2026Opt outLog in
RampedUp — Global Contact Data Solutions
Sign Up for Free

Blog

SHA-256 email matching for contact appends, and web identity for company appends

· 2 min read

RampedUp data appending, upgraded — SHA-256 email matching and web identity for companies

Two big upgrades to data appending just went live.

Now matching on SHA-256 hashed emails

We've long supported MD5 hashed emails for customers who can't share raw addresses. Now we support SHA-256 as well. Customers can send SHA-256 hashes, and we'll match and append on them just like plain-text or MD5 emails. SHA-256 is fast becoming the standard across ad platforms, CDPs and privacy-first data sharing, so this opens the door to many more customers and partners.

Web identity in company appends

A company's website is only part of how it shows up online. Web identity maps out a more complete web presence:

  • Canonical URL — the authoritative URL the company's site declares for itself.
  • Parked domains — domains tied to the company that now point to a parking service, with the source, where it resolves and when we last confirmed it.
  • Redirected URLs — domains that forward to another address, with the source, the destination and when we last resolved it.
  • Shortened URLs — short links tied to the company, such as bit.ly links, with when we last resolved them.
  • Social platforms — the company's social profiles, with the platform, the profile URL and when we last saw it.

Here's a real example. For The Dylan Whisky Bar, the URL thedylanwhiskybar.com redirected to thedylanwhiskybar.ie. Web identity connects those dots, which means better matching, cleaner domain data and a fuller picture for the company.

Available in the API and in CSV appends

In the API, web identity comes back as a structured webIdentity object:

"webIdentity": {
    "canonicalUrl": "https://thedylanwhiskybar.ie/",
    "parkedDomains": null,
    "redirectedUrls": [
      {
        "lastResolved": "2026-09-04T00:00:00",
        "redirectedTo": "thedylanwhiskybar.ie",
        "source": "thedylanwhiskybar.com"
      }
    ],
    "shortenedUrls": null,
    "socialPlatforms": null
}

CSV is harder, because complex, nested data doesn't fit neatly into a spreadsheet. There were two obvious options, and we rejected both:

  • Dropping raw JSON into a cell is hard to read and painful to work with in Excel.
  • Splitting every value into its own column (WebIdentity_RedirectedUrl1, WebIdentity_RedirectedUrl2 and so on) leaves you with far too many fields.

So we created a simple standard instead. There's one column per web identity area, a pipe (|) between entries and a tilde (~) between the parts of each entry:

  • WebIdentity_CanonicalUrl — a single URL
  • WebIdentity_ParkedDomains — source~resolvesTo~lastResolved
  • WebIdentity_RedirectedUrls — source~redirectedTo~lastResolved
  • WebIdentity_ShortenedUrls — url~lastResolved
  • WebIdentity_SocialPlatforms — domain~url~lastSeen

For example, a company with two shortened URLs looks like this:

https://bit.ly/4wcDabd~2026-08-02%7Chttps://bit.ly/4xF6yrK~2026-07-05

The redirect example above would look like:

thedylanwhiskybar.com~thedylanwhiskybar.ie~2026-09-04

You can read it at a glance, and in Excel it splits cleanly. Use TEXTSPLIT on the pipe to get one entry per row or cell, then on the tilde to get each part. Text to Columns works too. You get full detail without the column sprawl.

Both features are live now.

More on Product