Skip to main content

When setting up your JO program, it's crucial to have the right fields in place for accurate configuration. In this post, we'll explore the key sections and modules you need to consider. 

Question for Readers: What are some challenges you've faced when configuring JO programs with Query Builder, and how have you overcome them? Share your experiences and tips in the comments below!

 

Now, let's get into the essential fields for your JO program:

 

Using the Company Person Object in the Query Builder:

Company Details: Company ID ->

  • Company Name
  • Company GSID (or SFDC Account ID in case of SFDC)

CSM Details (Sender Details): Company ID ->

  • CSM Name (First Name, Last Name)
  • CSM Email
  • Calendly Link (if Applicable)
  • CSM GSID (If a CTA is to be triggered in the same program)

Company Person Details (Recipient Details): Person ID ->

  • Person Name (First Name, Last Name)
  • Person Email

Custom Field (Optional, based on use-case)

  • Tracking Link (for package delivery)
  • Subscription ID (for any purchases made)
  • Document Link

lq7gK5x5ToxzN-EDERQcVcmQr5l78PxMyuLJOw2myt7j9Cpjq4BgqTlAomN63E4ogURLqabDlI8Cf7P9KDoFhVGGRxefo_Lre5sXulB81y_4fC-n5YlC6fbjomLn43BRttmpWcKOYw4s-T-s7-WxPsM

Note: Configuring Company Details with SFDC

In cases where Company Details involve SFDC instead of MDA, SFDC Account ID will be obtained instead of Company GSID. The configuration approach slightly varies here. On the main page within the Source (when in the Green Box), you'll find a Gearbox icon at the top-right corner, next to the participant button.

  • If Standard Fields is not enabled, you'll encounter "External Account ID," which can be mapped with the SFDC account ID or any other relevant ID synced in the GS instance.

SO80EKtQZfT5tgfQKfDehSmq9mAqVKDytXLmHqvIsVozEp_-_KMyx4QrhmIOkAifBcZesP7dPxd436TtCQbKTVW_hBzA_1mbW5F1UbKVjTBvH9MqXn01fn_nH_DYib-7CJ2xvqNd1kKhnzQeHZgIanM

 

  • If Standard Fields are enabled, MDA Fields should be mapped.

k3kdhGe4r3Qa3iSjUdO3xLzz0X59zYQHSDh2lxFjZUvLKkMzb8GIPp5xhBqUUU-vzP3mQDPK99BHSLvwEnvik8_p1Xhgfsp39n5hf7cIM6km-0iWmmLo6-PGj4PH_fW-h5fwtPh39NVgMJmPumkz7NU

 

These fields will help you build a comprehensive and effective JO program using Query Builder. Now, don't forget to share your insights and experiences in the comments section – your input might just help others navigate their JO program configurations more smoothly!

I have a few things that I’ve learned:

  • If you are going to be using multiple queries, keep in mind you’ll need to map the same fields for each query.
  • If you have a csv that has limited account information, use the S3 bucket and Data Designer to load it, and add in any additional information from objects in the Data Designer.  Then, you can use the Data Designer object to build your query.
  • Before publishing your program, make sure you’ve covered what reporting needs your stakeholders are going to have for the program.  Is it just going to be standard opens and clicks or are they going to want additional details (CTAs and associated details, survey responses paired with cases or another object)?  This will also inform how you build your queries.

Reply


Terms & ConditionsCookie settings