# Integrating Krux with Salesforce Audience Studio ended on 1 February 2024. Do not build a connector. Data 360 is not a restore of Krux. **Published:** 2026-01-30 **Canonical:** https://synconai.com/integrating-krux-with-salesforce **Author:** SynconAI Architecture Team ## In short Audience Studio ended on 1 February 2024. Krux was that DMP. Do not build a connector. Do not call Data 360 a restore of Krux. Data Cloud was renamed Data 360 on 14 October 2025. Identity resolution is not a golden record and does not override source values. A call to the DMP cannot land. The other two pages cover files and the end of life. ## Sources - **Announcement: Salesforce Audience Studio DMP (Krux) End of Life is February 1, 2024** (retrieved 2024-02-01) https://docs.liveramp.com/connect/en/announcement--salesforce-audience-studio-dmp--krux--end-of-life-is-february-1%2C-2024--1-29-24-.html > Salesforce has officially announced that the End of Life date for Salesforce Audience Studio DMP (formerly known as Krux) is February 1, 2024. ## What to take away - Salesforce Audience Studio DMP, formerly Krux, ended on 1 February 2024. - Do not build a connector to it, and do not call Data 360 a restore of Krux. - Identity resolution is not a golden record and does not override source values. - The call cannot land. A diagram that loads the DMP, or restores it, is a poster. ## The guide A campaign brief still says to refresh the Krux segments before the send. The connector in the diagram loads audiences into a DMP that has already reached end of life, or it loads them into Data 360 and calls that load a restore. Both drawings are wrong. Audience Studio ended on 1 February 2024. Do not build a connector. Do not call Data 360 a restore of Krux. The call to the old DMP cannot land. The call that pretends Data 360 is Krux come back has renamed a different product into a poster. The person who briefed the refresh still has the segment names in a slide. The names are not a tenant. This page is about refusing the connector, not about choosing a new audience tool. The refusal comes first. A destination chosen in the same breath is how the restore sneaks in. ## The app There is no DMP app left to call. The announcement this page cites puts the name and the date in one sentence, quoted once: "Salesforce has officially announced that the End of Life date for Salesforce Audience Studio DMP (formerly known as Krux) is February 1, 2024." End of life was 1 February 2024. The announcement's date format stays inside the quotation. Formerly known as Krux means the DMP people mean when they say Krux is Audience Studio. You do not have a second, older Krux beside it. A connector from Krux into Audience Studio is a connector from a product into itself, aimed at a self that has ended. A search for a Salesforce Krux app is a search for that ended DMP. It is not a search for Data 360 under an old habit. Data Cloud was renamed Data 360 on 14 October 2025. Use the current name when you mean that product. The rename is not a restore of Krux, and it is not a reason to point the old segment job at Data 360. Data 360 is a different product, with its own page, for work you have actually decided to do there. This page does not make that decision. It stops the false one. Do not call Data 360 a restore of Krux. A Salesforce sandbox does not clone Data 360. Refreshing a core sandbox does not bring Audience Studio back, and it does not deposit Krux segments into Data 360. Anyone who says the sandbox already contains the old audiences should open it and show the DMP. The absence is the finding. The architecture that starts from a sandbox has started from the wrong system. ## The connector Do not build a connector. Not into Krux, not into Audience Studio, and not into Data 360 under the claim that the load restores what the DMP did. A connector needs a living system that expects the call. The DMP is not living. Data 360 does not become the DMP because a diagram says "audiences" on both boxes. The words can match and the products still differ. Identity resolution is not a golden record and does not override source values. If someone offers identity resolution as the way to stitch Krux back together, they have misnamed the feature and misnamed the job. It does not elect a winning value over the sources you hold. It does not resurrect a DMP. It is not the connector this brief is asking for. Leave it off this diagram. If you have a real identity question, it belongs to a Data 360 decision this page is not making, said in those plain terms, without the word Krux in the solution. This page does not name an API, a daily cap, a pixel host, a middleware SKU, or a price. The end-of-life announcement does not give them. A final load, a staging area inside the DMP, and a refresh job are all the connector. Refuse all three. A cap you invent to slow the load down is still a load. Slow does not make an ended system current. Write the line the campaign can read. We will not connect to Audience Studio. We will not connect to Krux. We will not treat Data 360 as a restore. The segment names on the slide are names, not a feed. If the campaign needs an audience decision, make it without this connector, from facts you can open, under a name that is not the dead DMP. ## The architecture The architecture is a retired DMP and a forbidden restore. Draw the end-of-life date. Do not draw a pipe into Audience Studio. Do not draw a pipe into Data 360 labelled Krux. A Salesforce Krux architecture diagram that shows segments arriving anywhere "as they used to" is a poster. | What the picture must say | What you write | | --- | --- | | System | None for Krux. Audience Studio ended on 1 February 2024. Data 360 is not a restore | | Object | None you can load. Do not invent a segment feed | | Failure | The call to the DMP cannot land | Data Cloud was renamed Data 360 on 14 October 2025. If Data 360 appears on a different picture, for a different job, that picture uses the new name and does not mention Krux as its source. If the only reason Data 360 is on this picture is the old DMP, remove it. A sandbox clone of Data 360 is not available as a place to hide the segments. A Salesforce sandbox does not clone Data 360. A guide book is not a segment map. People search for a Salesforce Krux integration guide book because DMP projects used to be thick. This page will not write the book, and it will not list traits, pixels, or destinations the announcement does not list. Thickness is not evidence. The announcement is short. The diagram should be short too. Identity resolution does not belong in a box on this poster, and neither does a golden record, because identity resolution is not a golden record. It does not override source values. A box that promises one customer record rebuilt from Krux has promised both a restore and a behaviour the feature does not have. Remove the box. You have not lost a diagram. You have lost a false one. ## When the call does not land The failure is a call that cannot land on the DMP. End of life was 1 February 2024. A load, a refresh, or a test connection aimed at Audience Studio or Krux does not get a retry policy. It gets a stop. Write the date as the cause. If a job is still scheduled, disable it. Do not point it at Data 360 in the same change and call the pointer a fix. The pointer is the restore this page forbids. A tag on a site that still names the old DMP is not a connector you should finish. It is a leftover. Note whether it fires, with the person who can publish the site. Firing into a host you cannot log into is not a landed integration. It is a leftover that needs an owner. The owner decides to remove it or to explain it without the DMP. They do not decide to complete it. Completing it builds the connector. Do not invent an error code, a match rate, or a daily volume. The announcement does not give them, and a match rate against a dead DMP would be theatre. If a screen shows a message, write the message you saw and the time. Then stop calling. Silence from an ended product is the expected failure. It is not a capacity incident, and it is not a cue to fail over into Data 360. If the campaign cannot wait, the campaign proceeds without this connector. Say that in the brief. A delay while a vendor designs a load is how the forbidden connector gets a weekend. There is no weekend load on this page. ## An integration names three things An integration exists only when the page can name the system, the object, and what happens when the call fails. A diagram that does not name those three is a poster. This page cannot name a live Krux system. It cannot name a live segment object you are allowed to load. It can name the failure: the call cannot land. That is not enough for an integration. Do not complete the trio by writing Data 360 in the system line and "Krux segments" in the object line. Data 360 is not a restore of Krux. The object would be a fiction. The diagram would still be a poster, only with a current logo on it. The same test rejects identity resolution as a disguised connector. You would be naming a feature, not a Krux object. And you would be naming it wrongly if you said it builds a golden record or overrides source values. Identity resolution is not a golden record and does not override source values. Leave the feature off this page. It does not make the ended DMP callable. Keep the table on the campaign brief. A vendor who adds a pipe has failed the test, even if the pipe is labelled temporary. Temporary loads into an ended DMP are loads. Temporary loads into Data 360 "so Krux is safe" are the restore. Both fail. Safe, in that sentence, means a different product chosen in a hurry. Hurry is not a source. ## The other two pages This page is not the implementation page, and it is not the page about what happened. Exports you can prove you hold, and the instruction not to migrate into the DMP, are on [the Krux implementation page](/krux-audience-studio-retirement). The end of life as history is on [what happened to Krux](/what-happened-to-krux). Stay here for the app, the connector, the architecture, and the call that cannot land. Do not let the Data 360 rename, dated 14 October 2025, rewrite the 2024 end of life. They are different sentences about different products. Link the other Krux pages when someone needs the inventory or the announcement. Do not link them as a single connector into Data 360. This page will not print a price for that connector, because the connector is refused. A partner who brings a guide book of segment syncs has brought the load. Ask them to show the DMP tenant they will call this week. They cannot, on this notice. If they show Data 360 instead, ask them to take the word Krux off the diagram and to admit they are proposing a different product. That proposal is not this page. It does not get approved as an integration of a DMP that ended on 1 February 2024. ::: warn Do not build a connector to Krux or to Audience Studio. End of life was 1 February 2024. Do not call Data 360 a restore. Identity resolution is not a golden record and does not override source values. A diagram of a load is a poster. ::: Put the end-of-life date on the brief and strike every arrow. If a job still runs, stop it without retargeting it. If a slide still says refresh Krux, replace the sentence with the date. Data 360 keeps its own name, on its own work, and does not inherit this connector. When the arrows are gone, stop. The campaign can ask for an audience decision in the open. It cannot ask this page to bring the DMP back. ## Questions ### What is the Salesforce Krux app? There is no current DMP. Krux became Salesforce Audience Studio, and end of life was 1 February 2024. Data 360 is not that app restored. ### What must a Salesforce Krux architecture diagram name? No live DMP, no segment object you can load, and a call that cannot land. Data 360 on the diagram as a restore of Krux makes the diagram a poster. A sandbox does not clone Data 360. ### What is a Krux Salesforce integration? A connector you should not build. Audience Studio ended on 1 February 2024. You cannot name a live system and a live object, so the integration does not exist. ### What is the Krux Salesforce integration connector? Do not build one, including a final load or a Data 360 restore. Identity resolution is not a golden record and does not override source values. This page names no API, cap, or price. ### Is there a Salesforce Krux integration guide book? This page is not a book of loads. The implementation page refuses a migration into the DMP. The other page is the end of life. Data Cloud was renamed Data 360 on 14 October 2025, which is not a Krux manual. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Data 360 (https://synconai.com/salesforce-data-360-services.html).