- If I'm not certain that all contacts on my external list exist in Dynamics, import a list of Contacts without allowing duplicates. This will insert any new records and throw errors for anyone who already exists. Not terrible.
- One consideration would be the use of a hidden admin text field like /Current Segment Admin Import Helper/ that I could, for example, set to /11-1-2023 Test Import/ for the sake of example. I would really, really like to be able to simply upsert this list (update existing based on email match to set this admin helper field; create new where existing contact isn't found) but this doesn't really seem possible. Is that still accurate?
- One consideration would be the use of a hidden admin text field like /Current Segment Admin Import Helper/ that I could, for example, set to /11-1-2023 Test Import/ for the sake of example. I would really, really like to be able to simply upsert this list (update existing based on email match to set this admin helper field; create new where existing contact isn't found) but this doesn't really seem possible. Is that still accurate?
- Starting to get stuck on how best to get these people into a place where I can send them an email.
- Ideal would be, I think, a Real Time segment. However:
- Unlike Outbound segments, I can't really define a 'static' segment to which I could mass add anyone with /11-1-2023 Test Import/ in a helper field. If I use this as an attribute it will change over time the next time I update a record with this value. If I try to manually select Contacts I need to click each record rather than setting up a query to one-time populate everyone with the value. Is the a way to do this in bulk with a helper field that I'm overlooking?
- I can't seem to find an N:N relationship table between Segment and Contact. These are kind of annoying to work with but could import [segment member] records using XRM ToolBox if I had a target table. Does this exist?
- Next option would be use an Outbound Segment which I think is probably my best bet
- Create a static segment, then use a query to add anyone with the admin helper field = /11-1-2023 Test Import/. Once Contacts have been added I won't need to worry about it in the future. Another alternative would be importing listmembers to a Marketing List, and then referencing that is the criteria for the Outbound Segment. However this seems kind of redundant and maybe would have storage implications if we used it heavily
- Main downside = splitting work across RT & Outbound, and the helper text field isn't the cleanest solution
- Also wondering if there's a way to directly import records to a junction table between Segment & Contact rather than using the helper field.
- Marketing Lists
- Benefit = has a visible N:N table I could import to
- Downside = I don't see a way to leverage a marketing list for a Real Time email send, other than create a dynamic Outbound segment based on the Marketing List membership. So I may as well just use the Outbound Segment to avoid 2x the number of records being created for a single send
- Connection
- Still wrapping my head around this but it seems like a multi-use junction table you can use for whatever (?) So in theory I could import Connection records linking Contacts <> Segments, and then use that as either a query in Outbound or add the Connections relationship as something that could be directly referenced in RT to build a dynamic segement.
- Upside = avoids admin helper field but fills a similar purpose
- Downside = volume of record storage if I'm maintaining a custom set of records that parallel Contact <> Segment relationship
- Ideal would be, I think, a Real Time segment. However: