
Company_key Approach In Endeca
Endeca identifies Accounts by their company_key
s.
It means when you create a segment based on your Fusion Registry ID
s, they
will be mapped to company_key
s and further processing will be done based on
those.
Example:
You have one Fusion Registry ID
(a.k.a. Fusion_Customer_Number) = 4386953 which is “INEOS MANUFACTURING DEUTSCHLAND GMBH”
On Endeca we would go like this:
Then we go and select newly created segment under “Company Segment Refinements”
And although we provided only one Fusion Registry ID
in the preview in the lower part of the screen, we can see some more. They all belong though to the same company_key = 13333795
Finally we end up with bigger number of available contacts because all contacts from all of the accounts under the same company_key
will be delivered.
Below are listed all other accounts for our example that share the same company_key
COMPANY_KEY | FUSION_CUSTOMER_NUMBER | ACCOUNT_NAME | CITY | COUNTRY |
---|---|---|---|---|
13333795 | A3MGLB5 | INEOS PHENOL GMBH | Gladbeck | GERMANY |
13333795 | 13333795 | INEOS DEUTSCHLAND HOLDING GMBH | Köln | GERMANY |
13333795 | 4102984 | STYROLUTION GROUP GMBH | Frankfurt | GERMANY |
13333795 | 4386953 | INEOS MANUFACTURING DEUTSCHLAND GMBH | Köln | GERMANY |
13333795 | 3444338 | INEOS PHENOL GMBH | GLADBECK | GERMANY |
13333795 | 3570499 | INNOVENE DEUTSCHLAND GMBH | Köln | GERMANY |
13333795 | 3432356 | INEOS GMBH | Köln | GERMANY |
13333795 | 13651139 | INEOS STYROLUTION GROUP GMBH | FRANKFURT A. MAIN | GERMANY |
If for some reasons you don’t want that behaviour and would like to strictly
stay with your Fusion Registry IDs
, you need to raise a “Custom List Request”
at GMSS Portal and
provide your specific ids as attachment there.