Skip to main content
Solved

Best set-up for two-sided marketplace on customer.io

  • March 21, 2023
  • 1 reply
  • 121 views
G

Hi everyone,

I just arrived on customer.io and I am at a crossroad in terms of set-up.

Basically, I have a two-sided marketplace in an “Airbnb-like” business, with travelers and hosts.

I need to have very different conversations and data models for travelers (welcome, reactivation, etc.) and hosts (e.g. finish onboarding, set correct prices etc.).

I am wondering about the best set-up on customer.io about this : what is the best way ? Should I create 2 different workspaces ? Should I look into objects ? Should I keep everything in one workspace on a “meta” data model for hosts and travelers ? 

I imagine this is quite a standard matter for all marketplaces.

Any recommendation and experiences to share on this ?
Thank you very much in advance !!

Guillaume

Best answer by Felix

Hey Guillaume,

I would definitley recommend to create two workspaces. This is exactly what they are made for. You can separate all the data without mixing them up.

Objects are like companies in a CRM, so in the end of the day, you would only associate a user to an object, but you would not send a message to the “objcet” / company. In your case though, you want to do this so I feel like this is not a good setup for you.

You could use objects for both workspaces, though. In the “host” workspace the objects are the travelers, in the “traveler” workspace the objects are the hosts. That way you can use the information of the counterpart to be displayed in messages.

 

Hope that helps,

Felix 🙂

View original
Felix
T
2 people like this
  • Felix
    Felix
  • T
    Tom
Did this topic help you find an answer to your question?

1 reply

Felix
  • Felix
  • Novice
  • 223 replies
  • Answer
  • March 22, 2023

Hey Guillaume,

I would definitley recommend to create two workspaces. This is exactly what they are made for. You can separate all the data without mixing them up.

Objects are like companies in a CRM, so in the end of the day, you would only associate a user to an object, but you would not send a message to the “objcet” / company. In your case though, you want to do this so I feel like this is not a good setup for you.

You could use objects for both workspaces, though. In the “host” workspace the objects are the travelers, in the “traveler” workspace the objects are the hosts. That way you can use the information of the counterpart to be displayed in messages.

 

Hope that helps,

Felix 🙂

More questions? Shoot me a message by clicking on my name. We are a certified customer.io agency. Happy to help!
G
1 person likes this
  • G
    GuillaumeJ

Reply


Most helpful members this week

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
Product
Resources
Industry
Company

Privacy PolicyTerms of ServiceStatus© Peaberry Software, Inc.

Terms & ConditionsCookie settings