Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

Value Transform

What does it do?

Values transforms enables a user to automate the process of manipulating and appending data, In Lehman’s terms its takes one bit of information and creates another. 

Who would use it?

Publisher, Agency users

Why would clients find this useful?

  1. By having this process, it cuts down manual work and data manipulation (Speed and time)
  2. Improves data quality and it becomes automated instead of manual intervention (improved data quality)
  3. Users do not need to change the way they collect data it means that the information they generate is standardized and they meet the clients needs (meets clients’ needs)

An example of how it would be implemented?

For a publisher, they would use this to make sure they don’t lose their data integrity.

If they capture information in a certain format for instance Company Size let’s say 1 to 50 but the client wants it to be 1 - 50 what value transforms would offer, is the ability to automatically create the new value without having to manually do it. Then once this info is added they integrate just the new info that’s was created.


Th user adds the value transform to the field they wants to generate data from for our example its company_size which if its triggered correctly will then adds the additional field clients_company_size


Then on the mapping, you put the values that as a publisher generates (keep data consistency) on the left and then on the right you add the format in which the client wants in.


This is a typical example of how they would use it, as you can see the field company size has come into the platform and in turn using the value transforms it has generated the field clients_company_size. Now the key point hear is that when the data is sent to the client you only mapped the new field that you have created.

 

For an agency, they may use this to automatically append a specific ID to a lead based off an asset the user had downloaded (content syndication) or on an integration front they may want to append a Salesforce campaign id or Marketo list id. With both of these examples its similar to the above in terms of making sure the data sent to exactly to the clients needs and rules.

In some cases, they use it to help with their reporting to add info if a lead with a certain job title comes into the platform eg CTO will append the information C-level management (in other words its good way to keep data consistent)

However with this functionality it can be applied to various different situations whenever the users needs to automate the process of manipulating data.


  • No labels