<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bigtable on Connor Charles</title><link>https://ccharlesgb.github.io/cc-portfolio/tags/bigtable/</link><description>Recent content in Bigtable on Connor Charles</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ccharlesgb.github.io/cc-portfolio/tags/bigtable/index.xml" rel="self" type="application/rss+xml"/><item><title>Identity stitching in a distributed environment</title><link>https://ccharlesgb.github.io/cc-portfolio/post/identity-stitching/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><guid>https://ccharlesgb.github.io/cc-portfolio/post/identity-stitching/</guid><description>&lt;p&gt;In this post, I will discuss how we use the identifiers attached to Snowplow events to build a consistent view of a consumer as they move between browsers and devices. The goal is to provide a single identifier for each consumer.&lt;/p&gt;
&lt;h1 id="what-is-identity-stitching"&gt;What is identity stitching?&lt;/h1&gt;
&lt;p&gt;Identity stitching in this context is the process of linking identifiers together from consumer data to build a unified view of each individual. When a consumer interacts with a website or app in Snowplow, the events they generate contain various identifiers such as cookies, mobile device IDs, and, if they are logged in, their account ID. Identity stitching allows us to link these together so that we have a single event timeline and profile for each consumer, even if they use multiple devices or browsers.&lt;/p&gt;</description></item></channel></rss>