CONTENT
  thinking about it, please hold on..

HTTP API within a Hierarchy context

Prerequisite

You should be familiar with general HTTP API inner workings.
You should be familiar with Hierarchy terminology and context.
It also helps to understand Attributes and Account Hierarchy.

You can find exact syntax for all items mentioned here in the Quick Reference Guide.

HTTP API with Hierarchy Specific considerations for Account attributes

All of the data that will be sent to Totango will use the same syntax as in the general HTTP API guide, with a few small exceptions.  I have highlighted the exceptions in yellow below.  Let’s examine this multi-product hierarchy diagram and identify the required data that should be sent for each level.

Parent Account

AccountID: required
Name: required *This requirement is only to establish name -- there is no need to send this in subsequent calls (unless the name changes).

All other attributes optional.

Parent-Sub Account (Child)

AccountID: required
Name: required *This requirement is only establish name, there is no need to send this in subsequent calls, unless the name changes.
ParentID: required (AccountID of the Parent Account) syntax: sdr_o.parent_id *This requirement is only to establish the parent, there is no need to send this in subsequent calls, unless the parent changes.

All other attributes optional.

Product Account

Account ID: See the Hierarchy glossary for choosing the Product AccountId.
Name: optional (dependent on Settings).
ParentID: required (AccountID of the Parent Account) *This requirement is only to establish the parent, there is no need to send this in subsequent calls, unless the parent changes.
ProductID: required *This requirement is only to establish the product, there is no need to send this in subsequent calls.

All other attributes optional.

Examples

Let’s use the hierarchy at right once again as an example and let’s assume that all account IDs are the same as the names mentioned in the diagram.

Example 1: Send attribute Industry to Parent Account.

https://sdr.totango.com/pixel.gif/?sdr_s=SP-0000-11&sdr_o=GHQ&sdr_o.Industry=Industrial

Example 2: Send attribute Success Manager to Child Account.

https://sdr.totango.com/pixel.gif/?sdr_s=SP-0000-11&sdr_o=Protractor&sdr_o.Success%20Manager=John%20Doe&sdr_o.parent_id=GHQ

Example 3: Send attribute Contract Value to Product Account.

https://sdr.totango.com/pixel.gif/?sdr_s=SP-0000-11&sdr_o=100_Denticon&sdr_o.Contract%20Value=30000&sdr_o.parent_id=Protractor&sdr_o.product_id=B

*Note that all levels require that you send data only to that level. You cannot send data about the Child Account via the Product Account or vice versa.

HTTP API with Hierarchy Specific considerations for Activity Tracking:

Your activity tracking will always flow in at the product account level.  Here is an example of how to send this data:

https://sdr.totango.com/pixel.gif/?sdr_s=SP-0000-11&sdr_o=100_Denticon&sdr_u=someone@somewhere.com&sdr_a=Login&sdr_m=Application

You can also intermix Product Account attributes within the tracking call:

https://sdr.totango.com/pixel.gif/?sdr_s=SP-0000-11&sdr_o=Protractor_B&sdr_u=someone@somewhere.com&sdr_a=Login&sdr_m=Application&sdr_o.Contract%20Value=30000&sdr_o.parent_id=Protractor&sdr_o.product_id=B
Have more questions? Submit a request

Comments

Follow
Powered by Zendesk