Changelog

Page 5 of 11

  • Persona sets are now downloadable as CSV

    Ben Rose
    Ben Rose
    on

    You can now easily download Faraday Personas as CSV files directly from the dashboard (a feature previously available only to API users).

    This update adds a "Download CSV" button on the Persona analysis page and in the Persona set menus, making it easier to access and export Persona data for reporting and analysis. The CSV format mirrors the layout of the Persona set analysis page, providing a more accessible and flexible way for both brands and agencies to integrate Persona data into internal reports, BI tools, and dashboards.

    Want to learn more? Check out this blog about how one of our partners, EmpowerFi™, has already started to generate value with the feature!

  • Improved persona charts

    Ben Rose
    Ben Rose
    on

    We've improved persona chart comparisons on the analysis page by ensuring consistency between persona charts and their corresponding column charts.

  • Data points summary card

    Ben Rose
    Ben Rose
    on

    We've improved data visibility and navigation by adding summary cards for data points to detail pages for cohorts and datasets. These changes mean you no longer have to return to list views to find important counts. The dataset data tab also now includes a sample data table, and connection information links directly to the used connection for easier access. Finally, we've refined summary item styles, making the interface cleaner and easier to read.

  • Recommended identifiers

    Zeb Pykosz
    Zeb Pykosz
    on

    When filling out a dataset's identity set form, we now automatically recommend columns based on what we detect in your dataset. This should make it easier to fill out the form and ensure that you are using the correct columns. Recommendations are based on simple pattern matching. For example, if your column name is email_address, we'll recommend using that column in the email identity property field. Note that these recommendations are not always perfect, so you should still review them before submitting the form. Not all columns will have recommendations.

    For more details, see the dataset API documentation under detected_columns.

  • Aggregation by USPS carrier route

    Faraday
    Faraday
    on

    Faraday now supports aggregation at the USPS carrier route level! Alongside postcode- and address-level aggregation, this provides another powerful way to customize enrichment and modeling coverage.

    View our documentation to learn more!

  • Score aggregation

    Andrew Becker
    Dr. Mike Musty
    Andrew Becker & 
    Dr. Mike Musty
    on

    This change improves percentiles and probabilities for scopes with outcome payloads by aggregating individual-level output at the residence and region levels.

  • Market Opportunity Analysis (MOA) endpoints

    Ben Rose
    Ben Rose
    on

    The Market Opportunity Analysis (MOA) API endpoints and UI integration have been implemented within Pipeline pages, allowing users to create, manage, and archive MOAs directly through the platform.

    View our documentation or API reference for more information.

  • Traits show page

    Ben Rose
    Ben Rose
    on

    This update introduces a new trait detail page in the Dashboard UI, making it easier for users to access trait analysis without digging into cohort creation. The page, located at /traits/ID, includes charts, general trait information, and a contribution card that highlights which datasets serve each trait—similar to the event streams detail page.

  • Batch-archiving on list pages

    Ben Rose
    Ben Rose
    on

    Some accounts have numerous unused resources and archiving one by one is tedious if the numbers are high. This update allows users to select multiple rows on list pages to archive various resources at once.

  • API support for outcome analysis by recognition level

    Faraday
    Faraday
    on

    In the API, an outcome’s performance can now be analyzed based on recognition level, which is broken down into all individuals (default), recognized individuals, and unrecognized individuals.

    • all_individuals: includes all individuals, regardless of recognition level.
    • recognized_individuals : individuals enriched with Faraday’s data
    • unrecognized_individuals : individuals with client-data only (no enrichment)

    The GET outcome analysis request will return the performance at each separate recognition level.