Hot answers tagged

14

Yes you can. In this post http://ggullentops.blogspot.be/2016/02/integrating-addthis-with-sitecore-goals.html I described how you can trigger a goal from AddThis (so actually using javascript to call a controller). A snippet from the controller code: var goalItem = ... // get goal item from Sitecore var visit = Tracker.Current; var page = Tracker.Current....


14

The beacon is created by taking a series of scripts and 'bundeling' them together (minifying and caching them). Have a look in App_Config\Include\FXM\Sitecore.FXM.Bundle.config .. this shows all the parts that go into the 'bundeling' process. This is the place you can add or modify any extra scripts you need to be delivered to the client as part of the ...


9

There are two ways to register goals from JavaScript that I am aware of: Federated Experience Manager Sitecore FXM allows you to make visits and trigger events from external websites. There's an FXM feature (that is not commonly used), allowing you to combine simultaneous site visits from the same browser into a single interaction. Visits will be combined ...


6

Be sure to use the MVC Form rendering rather than the Web Forms version, which is just named Form. The Web Forms version of the rendering is not supported for use with FXM. See the documentation: Add an MVC form to an external website with FXM


5

This is a general issue if you don't publish or you not configure Language rules. Please look on a attached picture how to configure Language rules.


4

Simon, I found an answer. There is an FXM variant of $(document).ready (more details here) So solution is to customize SearchBoxView and substitute existed inline js code with FXM-aware js code: <script type="text/javascript"> if (typeof (SCBeacon) != 'undefined' && SCBeacon && SCBeacon.push) { // Sitecore FXM ...


4

It turns out that there is a bug in Sitecore related to EXM and FXM files on the same instance. Sitecore Support pointed me to the following hotfix package that fixed the problem I was having: https://dl.sitecore.net/hotfix/Sitecore%20CMS%208.1%20rev.%20160519%20Hotfix%20119569-1.zip.


4

If you just want to validate if the page event was saved, you can run a MongoDB query against Interactions collection: db.Interactions.find({"$and": [ {"Pages":{"$elemMatch": {"PageEvents": {"$elemMatch": {"Name": "Your Goal Name"}}}}}, {"SiteName": "fxm"}] })


4

In a distributed environment, you must enable the following two configuration files on all the servers: Sitecore.FXM.Bundle.config Sitecore.FXM.config Also, make sure that the following configuration files are enabled on your content management servers: Sitecore.FXM.Speak.config Search configs (lucene files or solr files) In addition, on each content ...


3

Looking at the Sitecore.FXM.Bundle.config shows that the beacon is constructed via a processor in the preprocessRequest pipeline: <preprocessRequest> <!-- **** Bundles registered when they are first requested **** --> <processor type="Sitecore.FXM.Pipelines.PreProcessRequest.HandleBundleRequest, Sitecore.FXM" resolve="true"> ...


3

I have finally got a response from Sitecore: There is an inconsistency in Sitecore documentation regarding sitecore_fxm_web_index. Our documentation team is working to fix this inconsistency. FXM requires that both sitecore_fxm_web_index and sitecore_fxm_master_index are enabled in CM environment. It will take some time until existing WDPs are ...


2

The combination you described should be entirely possible. I encountered the same problem when implementing an FXM solution that triggered goals in Sitecore 8.2. Essentially there is a bug with the Rule OutcomeWasRegisteredDuringPastOrCurrentInteractionCondition The solution in this ticket mentions the fix in details for Sitecore 8.1 through to initial ...


2

I noticed in your solution RegisterConnectModelEvent is missing. RegisterConnectModelEvent is a Sitecore Commerce model for xConnect . Copy the file c:\inetpub\wwwroot\\XConnectModels\Sitecore.Commerce.Connect.XConnect.Models.json and Paste it to two locations to overwrite: C:\inetpub\wwwroot\.xconnect\App_data\jobs\continuous\IndexWorker\App_data\Models ...


2

We are able to fix this issue, though it was unique to our case, i thought it might be helpful to others who might have this problem. In FXM js code, the following code tries to set the sc_ext_contact cookie: cookies.set(extCookieName, resp.ContactId, { expires: new Date(Date.parse(e.ContactExpires)), path: '/' }); the Date.parse(e.ContactExpires) method ...


2

Client-side embedding (docs) is a technique that basically embeds a JSS app for client-side rendering within a Sitecore MVC rendering. This same technique (the resulting HTML for the Sitecore MVC rendering) should be fine to browser-side render the JSS app outside of Sitecore as well. Just make sure the API key allows the other app as a CORS origin. ...


2

Disabling config files is better option than deleting whole FXM folder. Just add ".disabled" extension to all config files under App_Config\Include\FXM folder Also don't forget to hide Federated Experience Manager from Launchpad for Content Editors: as after clicking on this button they will end up in this never ending loop: You can do it in "core" db by ...


2

You can use Robo 3T tool. Next example shows how to find goal by name in Interactions collection. db.getCollection('Interactions').find({Pages : {$elemMatch: {PageEvents:{$elemMatch:{Name:'FXMDemoGoal'}}}}})


2

Turns out whilst Sitecore 9.1 supports WAF configuration, it has a limitation where FXM tracking requests are blocked. Appears to be due to the page URL not being encrypted and it triggering Owasp security rules. It has been logged with Sitecore as a future feature request.


2

If your interaction doesn`t have WebVisit it is invisible in Experience Analytics by default. You can change you goal to a web interaction as @Chris Auer mentioned or remove(patch) <InteractionFilter type="Sitecore.ExperienceAnalytics.Aggregation.Filters.WebVisitFilter, Sitecore.ExperienceAnalytics.Aggregation" /> from Sitecore.ExperienceAnalytics....


2

Update your code as below, it works for me and I am able to see Goal in Experience Profile and in Experience Analytics Report as well. if (!Tracker.IsActive) { Tracker.StartTracking(); } if (Tracker.IsActive && Tracker.Current.CurrentPage != null) { Sitecore.Data.Items.Item goalItem = Sitecore....


1

So I did not find an outright "fix", however, I do have a workaround that enables this to work. In addition to the above httpProtocol section I posted in the description in the specific web.config file, I also created my own HttpHandler just for OPTIONS requests that come in. public class CoveoOptionsHandler : IHttpHandler { public bool IsReusable { ...


1

You need to set up rules for tracking. I faced the same issue then I write match rule to allow the external website request. Set up rules for tracking: In the Marketing Control Panel, you can set up the Federated Experience Manager to track only certain types of visits to your website, for example, visits from specific domains or visits referred from a ...


1

Ensure that the location of the Temp folder is in your \Website folder. use a relative path. For Sitecore 9 you can specify that in the FXM.BundledJSFilesPath setting in the Sitecore.FXM.config file. Probably the same for Sitecore 8.2, Else take a look at your config files and search for d:\local\temp you can also use the /sitecore/admin/showconfig.aspx url ...


1

For sites that are not managed or running on a Sitecore instance, you could use JSS in either: Headless SSR mode http://jss.sitecore.net/docs/fundamentals/application-modes#headless-server-side-rendering-mode API-only mode http://jss.sitecore.net/docs/fundamentals/application-modes#api-only-mode Which mode you choose would depend on how the non-Sitecore ...


1

Sitecore has acknowledged this as bug and provided a patch for SC8.2 update 1. Ask support for support ticket 507773 patch. Basically fix is use the FXM.Hostname if specified otherwise Current.Request.URL


1

Manged to fix this issue by steps below: Make sure you get 200 response from this call. If you get 301, review your redirect rule which could be removing trailing slash. https://mainsiteazurewebsites.net/sitecore/api/ssc/Beacon/Service/beacon/trackPageVisit/?contactId=&sessionId=&page=https%3A%2F%2Ftargetsite.azurewebsites.net%2Ffamilies%3Fsubcat%...


1

In general, historical personalization of users requires the data in xDB. You have a one-to-one relationship between xDB and Master database, so if you migrate your multiple sites into one multi-site authoring environment and publish out to individual content delivery instances and separate web databases, your front-end will still be isolated but you can ...


1

You need to set the FXM.Hostname setting to a hostname that is handled by your CD server. Use a config patch like this: <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <settings> <setting name="FXM.Hostname"> <patch:attribute name="value">mydomain.com</patch:attribute> ...


1

I had the same issue with some of the web-indexes. The indexes I was missing were: sitecore_web_index sitecore_marketingdefinitions_web sitecore_marketing_asset_index_web sitecore_fxm_web_index social_messages_web These are all defined in configuration files that are only deployed to the CD instances by the ARM templates. By default none of the indexes ...


1

Finally the error was resolved after installing a hotfix package please refer to below link using which my problem was resolved. Federated Experience Manager (FXM) won't start


Only top voted, non community-wiki answers of a minimum length are eligible