From 439268e207fbbfd51bac6549397ffe7c6a68a3e0 Mon Sep 17 00:00:00 2001
From: Trisha Pan <29530389+trisha@users.noreply.github.com>
Date: Wed, 2 Oct 2024 13:30:11 -0700
Subject: [PATCH] Update README.md

i spent too many hours trying to debug why i wasn't getting an email when i was cio.identify then cio.track and it's because i was generating a new id each time with the same test email (aka my inbox) to test that the email sent
---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 7df2a61..19ad449 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@
 ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/customerio)
 ![PyPI - Downloads](https://img.shields.io/pypi/dm/customerio)
 
-# Customer.io Python 
+# Customer.io Journeys Python 
 
 This module has been tested with Python 3.6, 3.7, 3.8 and 3.9. If you're new to Customer.io, we recommend that you integrate with our [Data Pipelines Python library](https://github.com/customerio/cdp-analytics-python) instead.
 
@@ -51,6 +51,8 @@ Only the id field is used to identify the customer here.  Using an existing id w
 a different email (or any other attribute) will update/overwrite any pre-existing
 values for that field.
 
+Note: If you use a different id but an email string that already exists for another Person, then no new Person will be created.
+
 You can pass any keyword arguments to the `identify` and `track` methods. These kwargs will be converted to custom attributes.
 
 See original REST documentation [here](http://customer.io/docs/api/track/#operation/identify)