- IP Geo-location - Do you have a meaningless IP address field in your data and you want some more valuable information from it? Did you know we add the client’s IP address to events sent from browsers and mobile devices? From this release you can enrich your data with an IP Geo-location lookup in the transform, and add State, Country, Continent, and Country Code. Check out how to do so in our Code Engine Documentation.
- Speaking of which - we added Code Engine documentation! We’re very proud of our powerful transform experience, where you can do everything from enriching and splitting your events to creating metrics and firing notifications. We felt like some of these capabilities may have been hidden from view, and we want you to get the full power, so check it out and start coding!
- Salesforce documentation - We were on a roll and also documented our Salesforce input. If you’re considering connecting your Salesforce, it’s got all the info you need.
- In an effort to make our Transform syntax more correct by Python standards, we changed our object field notation. Where once you may have written
event.field, we now only support
event['field']. We hope this aligns with your Python expectations!
- Notifications can have a lot of text, which we were wrapping quite strangely and cutting words in the middle. We fixed this so notifications expand to be beautiful and readable.
- We added path preview to the Azure input, to give you the extra info you need.
- We noticed that sometimes when we write transform code, we accidentally click back or navigate away, and we lose our outstanding updates. That can be incredibly frustrating, so we made the change that navigating away prompts you if you have unsaved changes.
- We fixed some issues with the table selector control on the mapping page.
- We removed an event type lock that stopped mappings from being applied.