In the CloudReco sample, TargetFinder.Stop() is called from OnTrackingFound() in the CloudRecoTrackableEventHandler.cs:

private void OnTrackingFound()
{
    ...

    // Stop finder since we have now a result, finder will be restarted again when we lose track of the result
    ObjectTracker objectTracker = TrackerManager.Instance.GetTracker<ObjectTracker>();
    if (objectTracker != null)
    {
        objectTracker.TargetFinder.Stop();
    }

    Debug.Log("Trackable " + mTrackableBehaviour.TrackableName + " found");
}

I´m using version 4.2.3. Therefor it should already be filtered, if I understood you correctly. (Even if I´d use SDK5 I would have overwritten the default behaviour).
Either way I´m implementing your code now in the "OnNewSearchResult" method, right?

I guess I´m getting a response in about 14 hours, since it takes about that long to review my post, like yesterday...

Our CloudReco sample app demonstrates the recommended way to avoid double-counting which is to call TargetFinder.Stop() once a successful reco occurs and while tracking is in progress. If you don’t stop TargetFinder after a successful reco, then the possibility that another reco request is sent for the same target will lead to additional recos being counted. Prior to SDK 5, the client filtered out a result that matched the currently tracked target. With SDK 5, you can now turn off that filtering for diagnostic purposes. See this article for more info:

https://developer.vuforia.com/library/articles/Solution/Vuforia-5-Migration

* In regards to forum posting, the changes were put into place as a result of large amounts of SPAM recently being posted to the forums. Additional improvements are under development as we work towards an effective solution for our forum community. Thanks for your input.

By the way: 

The new regulation, that ALL posts and replys have to be reviewed is absolutly not acceptable!

I´m not sure why you did this, since I didn´t notice much spam, but it heavily interferes a good and responsive communication between the developers.

Hi

thanks for answering.

I call 

mImageTracker.TargetFinder.ClearTrackables (false);

and 

QCARBehaviour.enabled = false;    

I think that´s how it´s is done in the sample I was building up upon. Did this change in a way that this could result into multiple trackings?!

Because: The behaviour of the app is ok, and it effectivly stops tracking as far as I can tell by the console.

Since we will reach 100% of our Cloud-plan today and will apparantly have to pay for all extra trackings (since no support answered me on my question for a special regulation), there are some angry faces here...

Please answer me if I have to use the line you wrote, since it is very hard to test, since the Target-Database lags behind.

Best regards

Maik

When the target in question is recognized, does TargetFinder.Stop() get called to prevent any more frames being sent to the cloud?